You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2018/07/06 15:53:00 UTC

[jira] [Resolved] (SLING-7766) Optimise the way the AntiSamy configuration is read

     [ https://issues.apache.org/jira/browse/SLING-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu resolved SLING-7766.
---------------------------------
    Resolution: Fixed

Implemented in [commit 61dd6a9|https://github.com/apache/sling-org-apache-sling-xss/commit/61dd6a9].

> Optimise the way the AntiSamy configuration is read
> ---------------------------------------------------
>
>                 Key: SLING-7766
>                 URL: https://issues.apache.org/jira/browse/SLING-7766
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: XSS Protection API 2.0.10
>
>
> Currently the AntiSamy configuration is expected to be at {{sling/xss/config.xml}}, relative to the search paths. However, users should decide themselves where they want to store this file.
> The default should still be {{sling/xss/config.xml}}, however an OSGi configuration should allow to define any other path.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)