[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061880#comment-13061880
]
Noah Slater commented on COUCHDB-1175:
--------------------------------------
"Both text/html and application/json have the same preference value (1.0).
Whichever way we jump, something goes wrong."
I disagree. If the q value is the same, we get to pick which one we want to
serve up. In this instance, we assume it is a browser request, so we serve up
HTML. What is the problem in only serving up JSON if application/json or
application/* has a higher q value than the text/html or text/* media types? Is
there a use case this does not work for?
Also, Jason... 7 coolpoints for you, sir.
> 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
