[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051198#comment-13051198
]
Marcello Nuccio commented on COUCHDB-1175:
------------------------------------------
"Accept: text/html, */*"
Both 'text/html' and 'application/json' have a q-value of 1,
they are exactly equally preferred. What to do?
Common sense says to me: get the best match first.
"text/html" is an exact match, so I tend to say the client prefers it over the
generic "*/*". How-to explain its inclusion otherwise, given that "*/*"
includes "text/html"?
> 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
