[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051165#comment-13051165
]
Marcello Nuccio commented on COUCHDB-1175:
------------------------------------------
Sorry if I gave the impression of being harsh. I only wanted to be very clear,
because I am always concerned for my bad English.
The change was deliberate but has unintended side-effects. I'm
currently +1 on reverting this change in 1.1.1, but I'd like to
finally nail the exact semantics for this content-type negotiation
once and for all.
As I said in my first comment, I think the only problem here is that we are
ignoring the value of "q". This is wrong since it is not standard compliant.
Unfortunately I have still to learn Erlang so I am not sure I can propose a
patch for this...
> 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
> Fix For: 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
