[
https://issues.apache.org/jira/browse/SLING-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750961#action_12750961
]
Felix Meschberger commented on SLING-1096:
------------------------------------------
Explicitly set the sling.servlet.prefix to "-1" for the Sling default servlets:
SlingPostServlet, DefaultGetServlet, JsonQueryServlet, and RedirectServlet in
Rev. 810875
> Sling servlets (default GET, POST, etc.) should registered last on the search
> path
> ----------------------------------------------------------------------------------
>
> Key: SLING-1096
> URL: https://issues.apache.org/jira/browse/SLING-1096
> Project: Sling
> Issue Type: Improvement
> Components: Samples, Servlets Get, Servlets Post
> Affects Versions: Servlets Get 2.0.2, Servlets Post 2.0.2, Scripting
> JavaScript 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Servlets Get 2.0.6, Servlets Post 2.0.6
>
>
> Default GET and POST servlets are currently registered with the
> sling/servlet/default resource type and the respective request method (or
> extension for GET servlets). This registers these servlets under /apps and
> prevents any custom registered servlets for these resource types.
> As of SLING-910 we have the option to control the absolute path prefix used
> for servlet registration. As such it would probably make perfect sense to
> register the Sling default servlets under the last entry in the search path
> by setting the following registration property:
> sling.servlet.prefix = -1
> This allows for custom provided servlets registered at sling/servlet/default
> to be injected in to the servlet resolution candidates.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
