[jira] [Resolved] (SLING-2695) SlingServletResolver Logging

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

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

Carsten Ziegeler resolved SLING-2695.
-------------------------------------
    Resolution: Won't Fix

> SlingServletResolver Logging
> ----------------------------
>
>                 Key: SLING-2695
>                 URL: https://issues.apache.org/jira/browse/SLING-2695
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>    Affects Versions: Servlets Resolver 2.2.0
>            Reporter: Dan Klco
>            Priority: Minor
>              Labels: patch
>         Attachments: SLING-2695.diff
>
>
> There are two odd things (to me at least) about the Sling Servlet Resolver.  First, the logger for this class is public static final, which means it is effectively a global variable.  It is actually referenced outside the class in the AbstractResourceCollector.  
> Second, when the Sling Servlet Resolver is going to resolve a request and if finds that the request path is not in the servletresolver.paths set of allowed paths, it sends a log message to the getRequestProgressTracker, but I would think it should log at least an info message to the logs, letting the developer know that the script is not going to be executed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)