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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: HTTP Interface
• Skill Level: Regular Contributors Level (Easy to Medium)
• Assignee: Unassigned
• Reporter: Robert Newson
• Created: 12/Aug/09 11:36
• Updated: 02/Sep/18 06:26
• Resolved: 02/Sep/18 06:26

Description

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.