[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228349#comment-14228349
]
ASF GitHub Bot commented on COUCHDB-1175:
-----------------------------------------
Github user rnewson commented on the pull request:
https://github.com/apache/couchdb/pull/284#issuecomment-64907484
I'm all for improving this, I filed COUCHDB-1175 myself because neither the
behavior before or after the original change here satisfied every use. That
ticket, as you can see, ran aground without really solving the problem. I
simply don't know if there's a solution that works correctly for all the cases.
Is it your claim that there is, given that browsers send Accept with */* and
usually without q values?
> 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
> Priority: Blocker
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
