[
https://issues.apache.org/jira/browse/COUCHDB-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739742#action_12739742
]
Noah Slater commented on COUCHDB-453:
-------------------------------------
What do you mean when you say CouchDB will fall back to the "first mime type
provided"? Do you mean the first media type in the configuration, or the first
media type provided by the client on the Accept header? If you mean the first,
why would we not send back a 406 Not Acceptable header? If a client is
specifically requesting a certain media type, that we cannot fulfil, I think it
makes more sense to tell them that we cannot fulfil the request. If it is the
latter, does Erlang not have any content negotiation libraries we can hook into
so that we can properly parse client and server q-values?
> If "Accept: foo" header is sent, server returns a render_error
> --------------------------------------------------------------
>
> Key: COUCHDB-453
> URL: https://issues.apache.org/jira/browse/COUCHDB-453
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Jason Davies
> Attachments: render.js.patch
>
>
> The full error is: {"error":"render_error","reason":"function raised error:
> [object Object]"}
> This occurs because there is no match for the "foo" mime type. Simple patch
> to follow that makes us fall back to sending the first mime type provided.
> "Be conservative in what you send, liberal in what you accept".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
