[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051471#comment-13051471
]
Benoit Chesneau commented on COUCHDB-1175:
------------------------------------------
Rather than "reverting the change" we should introduce a complete check of
accepted mime-types and also what are content-types accepted on each
responses. Rather than specifically solving authentication redirection (which
is imo a bad hack) we should take the 3 months we have before 1.2 to take the
time for that. I will attach later today an editable list of expected response
/ API calls so we can eventually start on it.
Anyway, changing Authorization header in settings, is enough most of the time.
The application can already catch this authorization error and choose to use
another page for authentication or just authenticate directly in ajax. And this
setting was added was added to solve this specific case and allowing cookie
authentication via ajax. We don't have really need for this redirection which
was introduced as a convenience and I think it's perfectly safe on an api point
of view to just remove it.
> 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
