couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johannes J. Schmidt (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1175) Improve content type negotiation for couchdb JSON responses
Date Sat, 18 Jun 2011 09:22:47 GMT


Johannes J. Schmidt commented on COUCHDB-1175:

Hey come on, this is a very relevant bug. For me its a blocker to use 1.0.2 until this is

My scenario:
I have a CouchApp and give my users their own dbs, which they can secure if they want to.
Behind a vhost I route to a list function inside the db myfairuser.
Now imagine myfairuser is secured. How can you login there?
Don't tell me the user has to return to after reading the nice {"error":"unauthorized","reason":"You
are not authorized to access this db."} using the browser navigation.

g jo

> Improve content type negotiation for couchdb JSON responses
> -----------------------------------------------------------
>                 Key: COUCHDB-1175
>                 URL:
>             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
> We should follow the standard.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message