sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SLING-1974) Accept header issues in the Sling POST Servlet
Date Wed, 09 Feb 2011 16:07:57 GMT

     [ https://issues.apache.org/jira/browse/SLING-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Felix Meschberger updated SLING-1974:
-------------------------------------

          Component/s: Servlets
    Affects Version/s: Servlets Post 2.1.0
        Fix Version/s: Servlets Post 2.1.2

> 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
>
>
> 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

        

Mime
View raw message