[
https://issues.apache.org/jira/browse/SLING-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610792#comment-16610792
]
Robert Munteanu commented on SLING-6767:
----------------------------------------
Since [~joerghoh], [~kwin] and myself are all at adaptTo we took the
opportunity to have a quick discussion about this. To sum up the main points:
- the problems appear when the servlet/script that handles the request is not
the precise one that the client intended
- usually the problems are caused by the Sling Default POST Servlet, but not
always
- a less intrusive solution would be to allow the client to say that it
requires "precise" script resolution and reject the possibility of it being
served by a less specific handler
- for requests accessing existing resources, the resource type is known from
the repository
- for requests creating resources, the resource type is known from the request
(although this might be non-generic, TBD)
The proposed solution is to allow the client to set an HTTP header which
specifies the type of resolution to use (provisional names):
- default ( what we have today )
- precise ( the script/servlet must exactly match the resource type )
- relaxed ( what we have today, excluding the default resource type )
We discussed adding a request parameter but were not convinced that it is
necessary, since now it's possible to add headers to requests in all relevant
scenarios ( programatically, browser requests, developer tools ) and we can
always add it later. Removing it after a release would be more problematic.
> 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)
