[
https://issues.apache.org/jira/browse/SLING-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611771#comment-16611771
]
Robert Munteanu commented on SLING-6767:
----------------------------------------
{quote}In other words, is this a decision the client should make, or the
administrator?{quote}
First of all, I think this is an edge scenario we're trying to handle - 99% of
the time this option will not be needed - things will "just work". So I would
expect that whenever this is needed both the client and server will know.
The difference is in where the knowledge about this kind of requests is held.
If we do this on the server we'll have "yet another configuration option",
whereas on the client we would clearly validate the expectations. Another
complication on doing this on the server side is that configuration will get
complicated:
- do we want paths?
- do we want paths + sub-paths?
- do we want resource types?
- do we want to differentiate on HTTP methods?
By moving this to the client we remove the need for all this complexity.
> 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)
