[
https://issues.apache.org/jira/browse/SLING-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610868#comment-16610868
]
Eric Norman commented on SLING-6767:
------------------------------------
A way to enforce a "precise" (or strict) script/servlet resolution is a good
idea. But I think I would prefer a way to enable it system wide that doesn't
have to be turned on for each request. In other words, is this a decision the
client should make, or the administrator?
In my own project I've been utilizing a BlockPOST servlet that is registered
for each resource type that I use which stops a POST request from falling
though to the default handler for unexpected selectors. The proposal from
[~rombert] seems to have similar goals.
> Jackrabbit Usermanager: Allow to detect whether a POST request was treated by
> the default POST servlet or the jackrabbit.usermanager
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-6767
> URL: https://issues.apache.org/jira/browse/SLING-6767
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.8
>
>
> Currently it is impossible to tell from the response whether a POST request
> has been answered by either the Default Sling POST servlet or the Jackrabbit
> Usermanager. Both the JSON and the HTML look exactly the same no matter, who
> answered. It should be possible to see from the client-side whether a request
> has been treated by one or the other.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
