"content-type" header behavior from external processes is poorly defined
------------------------------------------------------------------------
Key: COUCHDB-552
URL: https://issues.apache.org/jira/browse/COUCHDB-552
Project: CouchDB
Issue Type: Bug
Components: Infrastructure
Affects Versions: 0.11
Environment: CentOS5.3, Erlang R12
Reporter: Christopher O'Connell
Priority: Minor
Fix For: 0.10.1
When returning headers from an external process, the behavior depends on
capitalization, and is radically different in each case.
Consider the external process return
a: { "code":200, "json": { "hello":"world" }, "headers": {} }.
If returned as (a), the server serves { "hello":"world" } with header
"Content-Type: application/json".
If the json is modified to
b: { "code":200, "json": { "hello":"world" }, "headers":
{"Content-type":"text/plain"} }
c: { "code":200, "json": { "hello":"world" }, "headers":
{"content-type":"text/plain"} }
If returned as (b) or (c), the server serves { "hello":"world" } with header
"Content-Type: text/plain, application/json".
If the json is modified to
d: c: { "code":200, "json": { "hello":"world" }, "headers":
{"Content-Type":"text/plain"} }
If returned as (d), the server serves { "hello":"world" } with header
"Content-Type: text/plain".
There should be one well defined behavior when a "content-type" header is
returned from an external process.
To reproduce this error, setup an external process and return json strings as
specified above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
