[
https://issues.apache.org/jira/browse/SLING-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992981#comment-12992981
]
Alexander Klimetschek commented on SLING-1974:
----------------------------------------------
@Carsten: I (and Bertrand, IIUC) meant server-side prefs only for conflicts in
the accept header (i.e. two mime-types with equal weight), where as per the
HTTP spec there is no preference given by the client. So it's perfectly fine to
use a server preference in this case. As noted in the link from Jukka, this
will make the response stable (even if you consider the request to be "broken"
in this case). Currently the handling is also decided by the server - by
sorting alphabetically by the mime-type - hence it is stable, but not
configurable.
On the other hand, I guess this is a very specific case, and is in most cases
better solved by fixing the client or supporting the simpler extension-based
selection of response types.
> Accept header issues in the Sling POST Servlet
> ----------------------------------------------
>
> Key: SLING-1974
> URL: https://issues.apache.org/jira/browse/SLING-1974
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Post 2.1.0
> Reporter: Felix Meschberger
> Fix For: Servlets Post 2.1.2
>
> Attachments: SLING-1974.patch
>
>
> As of SLING-1336 the Sling POST Servlet can interpret the Accept request
> header to select what response content type to render.
> Unfortunately that handling seems broken as for an Accept header like (as
> generated by FireFox with the JSONovich plugin installed) :
> Accept:
> text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8,application/json
> the JSON response might be selected but sometimes also text/html (we can
> observe both behaviours for different server platforms with our application).
> The Accept header should probably consider equivalent q values (as for
> text/html and application/json in the example) to solve the tie by selecting
> the first type list; thus text/html in this example.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
