You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/04/26 10:38:04 UTC

[jira] [Resolved] (SLING-6794) Inconsistent handling of default configuration

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

Carsten Ziegeler resolved SLING-6794.
-------------------------------------
    Resolution: Fixed
      Assignee: Carsten Ziegeler

Fixed in rev 1792725

> Inconsistent handling of default configuration
> ----------------------------------------------
>
>                 Key: SLING-6794
>                 URL: https://issues.apache.org/jira/browse/SLING-6794
>             Project: Sling
>          Issue Type: Bug
>          Components: XSS Protection API
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: XSS Protection API 1.0.20
>
>
> The XSSFilterImpl has currently an inconsistent handling of default configurations:
> If a login exception for the service resource resolver occurs, there is no configuration at all - which I think is wrong. The default config should apply or an exception should be thrown, but I guess applying the default config is the better option
> In addition we might want to reduce the log level from WARN to INFO or even DEBUG when there is no configuration in the resource tree but the embedded default is used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)