[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114441#comment-13114441
]
matthew o'gorman commented on COUCHDB-1175:
-------------------------------------------
It's unfortunate if this is marked as won't fixed as it will make secure
couchapps far more difficult to setup. The current options as I understand it
require you having a http proxy in place as well as a second db that is set to
not allow writes that can connect to the _users table to allow the user to log
in and then redirect back to the main real app. I realize that there seems to
be no clean solution to the problem but it does seem important at least for the
people who want to write apps that are direct couchdb applications.
> 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
