couchdb-dev mailing list archives

[jira] Updated: (COUCHDB-463) Allow client to insist on Content-Type: application/json in all responses

Date

Sat, 09 Oct 2010 19:46:47 GMT

[ https://issues.apache.org/jira/browse/COUCHDB-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis updated COUCHDB-463:
--------------------------------------
Skill Level: Regular Contributors Level (Easy to Medium)
> Allow client to insist on Content-Type: application/json in all responses
> -------------------------------------------------------------------------
>
> Key: COUCHDB-463
> URL: https://issues.apache.org/jira/browse/COUCHDB-463
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Reporter: Robert Newson
>
> The Content-Type of responses is negotiated via Accept (application/json if acceptable,
text/plain if not). When the client is the browser, this often fails as the Accept line usually
does not include application/json.
> Consider a query parameter to force application/json responses even without the Accept
header. Couchdb-lucene does this today (it didn't do it yesterday), described as;
> "force_json
> Usually couchdb-lucene determines the Content-Type of its response based on the presence
of the Accept header. If Accept contains "application/json", you get "application/json" in
the response, otherwise you get "text/plain;charset=utf8". Some tools, like JSONView for FireFox,
do not send the Accept header but do render "application/json" responses if received. Setting
force_json=true forces all response to "application/json" regardless of the Accept header."
> I recognize it duplicates the HTTP content negotiation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.