couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Chesneau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1175) Improve content type negotiation for couchdb JSON responses
Date Mon, 23 May 2011 10:50:47 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037885#comment-13037885
] 

Benoit Chesneau commented on COUCHDB-1175:
------------------------------------------

that's only part of the problem.

1. Do we want to accept text/plain where we send json . imo we should rather send 406. Wich
is more restful. The problem is that it introduce some incompatibilities with previous releases..
The same for html/text plain, if this is the content we want to send then we shouldn't accept
to return other content types .  All of this could alos exists in the way we manage content
types in shows and other functions.

3. Auth. Since auth redirect is only useful for html content, we should better redirect only
on html content and return 401 instead. This part is fixed in trunk.

About this function, do we want that upstream or only couch ?





> 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

Mime
View raw message