You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/05/11 21:34:48 UTC
[jira] [Resolved] (SLING-2472) RequestProgressTracker output is
confusing for servlet mounted on a path that's not configured for execution
[ https://issues.apache.org/jira/browse/SLING-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-2472.
----------------------------------------
Resolution: Fixed
Fixed in revision 1337343, the following message is now added to the RequestProgressTracker in this case:
1 (2012-05-11 12:22:58) LOG Will not look for a servlet at /testing/PathsServlet/foo.servlet as it is not in the list of allowed paths
The message might not appear in all resolution scenarios with my patch, but it's at least an improvement.
> RequestProgressTracker output is confusing for servlet mounted on a path that's not configured for execution
> ------------------------------------------------------------------------------------------------------------
>
> Key: SLING-2472
> URL: https://issues.apache.org/jira/browse/SLING-2472
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Resolver 2.1.2
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Servlets Resolver 2.1.4
>
>
> Given a PathsServlet with path=/testing/PathsServlet/foo and a SlingServletResolver config that does not include that path in the list of executable ones, the RequestProgressTracker outputs info like this when making a request on that path:
> Request 63 (GET /testing/PathsServlet/foo.html) by anonymous - RequestProgressTracker Info
> ...
> 0 (2012-05-11 12:27:44) TIMER_START{resolveServlet(ServletResource, servlet=org.apache.sling.launchpad.testservices.servlets.PathsServlet, path=/testing/PathsServlet/foo)}
> 2 (2012-05-11 12:27:44) TIMER_END{2,resolveServlet(ServletResource, servlet=org.apache.sling.launchpad.testservices.servlets.PathsServlet, path=/testing/PathsServlet/foo)} Using servlet Sling Core Default Servlet
> ...
> 2 (2012-05-11 12:27:44) TIMER_END{2,ServletResolution} URI=/testing/PathsServlet/foo.html handled by Servlet=Sling Core Default Servlet
> which makes it hard to understand why the PathsServlet is not used. The fact that the path is not authorized for execution should be indicated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira