You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Christopher O'Connell (JIRA)" <ji...@apache.org> on 2009/11/02 01:28:59 UTC
[jira] Created: (COUCHDB-552) "content-type" header behavior from
external processes is poorly defined
"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.
[jira] Commented: (COUCHDB-552) "content-type" header behavior from
external processes is poorly defined
Posted by "Christopher O'Connell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772401#action_12772401 ]
Christopher O'Connell commented on COUCHDB-552:
-----------------------------------------------
I'll try a build and let you know.
It's probably not necessary to push it to 0.10.1, but a note on the wiki would be nice.
> "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
> Assignee: Adam Kocoloski
> 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.
[jira] Assigned: (COUCHDB-552) "content-type" header behavior from
external processes is poorly defined
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Kocoloski reassigned COUCHDB-552:
--------------------------------------
Assignee: Adam Kocoloski
> "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
> Assignee: Adam Kocoloski
> 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.
[jira] Closed: (COUCHDB-552) "content-type" header behavior from
external processes is poorly defined
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Kocoloski closed COUCHDB-552.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.10.1)
0.11
Thanks, I updated the wiki with something similar. The wiki is publicly editable, too -- no need to wait for a committer in that case! Best,
Adam
> "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
> Assignee: Adam Kocoloski
> Priority: Minor
> Fix For: 0.11
>
> Attachments: ExternalProcesses.txt
>
>
> 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.
[jira] Updated: (COUCHDB-552) "content-type" header behavior from
external processes is poorly defined
Posted by "Christopher O'Connell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher O'Connell updated COUCHDB-552:
------------------------------------------
Attachment: ExternalProcesses.txt
Here's the external process wiki page with relevant edits.
> "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
> Assignee: Adam Kocoloski
> Priority: Minor
> Fix For: 0.10.1
>
> Attachments: ExternalProcesses.txt
>
>
> 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.
[jira] Commented: (COUCHDB-552) "content-type" header behavior from
external processes is poorly defined
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772394#action_12772394 ]
Adam Kocoloski commented on COUCHDB-552:
----------------------------------------
Hi Christopher, this should already be fixed in trunk. If you're building from source can you svn up and try again?
I didn't backport the fix to the 0.10 branch. If folks think the bug is serious enough we can certainly include the fix in 0.10.1.
> "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
> Assignee: Adam Kocoloski
> 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.