[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051482#comment-13051482
]
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 fixed.
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 example.com/myfairuser 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 example.com 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: 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
