[
https://issues.apache.org/jira/browse/SLING-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608491#comment-16608491
]
Jörg Hoh commented on SLING-6767:
---------------------------------
[~edn]: If the client does not express it's expectation the server will return
an agnostic message plus a statuscode. If the client want's to be more specific
about its intention (and in case get a more specific error message) the client
should provide this pre-condition. It's not about trust.
Of course we could add a filter to validate that. But what gives you the
assurance that the filter is installed (in case the usermanager isn't)? And
then it's not only the usermanager, but also other servlets or services, which
one might want to test for.
All this should be built into the framework but it a way that it can be applied
safely without knowing the individual functionality at all. And if it's not
about error cases here (as I understand Konrad's issue) the response should be
made unique in a way that the caller can detect the difference.
> 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)
