couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Chesneau <bchesn...@gmail.com>
Subject Re: [jira] [Created] (COUCHDB-1175) Improve content type negotiation for couchdb JSON responses
Date Fri, 08 Jul 2011 12:02:21 GMT
mmm no the change i made do what nslater describe.

On Friday, July 8, 2011, Robert Newson (JIRA) <jira@apache.org> wrote:
>
>     [ https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061883#comment-13061883
]
>
> Robert Newson commented on COUCHDB-1175:
> ----------------------------------------
>
> that flips the behavior back to 1.0.x style. It was flipped in 1.1.x to address an issue
with jquery (iirc). Benoit made the change, he should chip in with a better explanation.
>
>
>> 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
>
>
>

Mime
View raw message