Bertrand Delacretaz created SLING-2472:
------------------------------------------
Summary: 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
