[ 
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052442#comment-13052442
 ] 

Marcello Nuccio commented on COUCHDB-1175:
------------------------------------------

Jason, I am still convinced that full support for Accept header is a good 
thing. But I am also convinced that good support for all clients is a good 
thing too.

The patch of Filipe is very welcome, but maybe it is not enough. For example, 
if I do a GET on

    http://localhost:5984/db/_design/app/page.html

I think it is reasonable to expect an HTML response without knowing what the 
Accept header is.  It is reasonable because it works everywhere... well... I 
hope so... :-)

> Improve content type negotiation for couchdb JSON responses
> -----------------------------------------------------------
>
>                 Key: COUCHDB-1175
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1175
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 1.0.2
>            Reporter: Robert Newson
>            Assignee: Robert Newson
>            Priority: Blocker
>             Fix For: 1.1.1, 1.2
>
>
> Currently we ignore qvalues when negotiation between 'application/json' and 
> 'text/plain' when returning JSON responses.
> Specifically, we test directly for 'application/json' or 'text/plain' in the 
> Accept header. Different branches have different bugs, though. Trunk returns 
> 'application/json' if 'application/json' is present at all, even if it's less 
> preferred than 'text/plain' when qvalues are accounted for.
> We should follow the standard.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to