[
https://issues.apache.org/jira/browse/SLING-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992999#comment-12992999
]
Alexander Klimetschek commented on SLING-1974:
----------------------------------------------
If we don't want to change the API at this point, we could just leave out
adding getResponseContentType(String.. supported) and do this logic inside the
SlingPostServlet. A utility method taking both the getResponseContentTypes()
enumeration and an ordered list of supported types from the servlet is probably
better than putting this into the request API.
Then you only have to adapt the implementation for
getResponseContentType()/getResponseContentTypes() to add 2. (accept header).
I think we have too many filters already, makes the stack traces so long ;-)
BTW: Is getResponseContentType() / getResponseContentTypes() used for the
servlet resolution? (mapping mime-types back to plain extensions)
> 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
