couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-87) Should not send transfer-encoding: chunked to an HTTP/1.0 client.
Date Fri, 27 Jun 2008 17:39:45 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608851#action_12608851
] 

David Reid commented on COUCHDB-87:
-----------------------------------

Ok, so with telnet the connection gets severed correctly.  Perhaps it is getting severed with
paisley too and something else is going wrong because it received chunked data.  However

However couchdb built from the 0.8.0 tarball definitely exhibits this behavior. I've tested
with and without a count argument and both are using the chunked Transfer-Encoding.

$ telnet localhost 5984
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying fe80::1...
telnet: connect to address fe80::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /mydb/_all_docs HTTP/1.0

HTTP/1.0 200 OK
Transfer-Encoding: chunked
Server: MochiWeb/1.0 (Any of you quaids got a smint?)
Date: Fri, 27 Jun 2008 17:33:59 GMT
Content-Type: text/plain;charset=utf-8

94
{"total_rows":2,"offset":0,"rows":[
{"id":"0efd8309b5bf3de2f46374b38bcfa88b","key":"0efd8309b5bf3de2f46374b38bcfa88b","value":{"rev":"1770569613"}}
3b
,
{"id":"mydoc","key":"mydoc","value":{"rev":"541388443"}}
4

]}
0

Connection closed by foreign host.


> Should not send transfer-encoding: chunked to an HTTP/1.0 client.
> -----------------------------------------------------------------
>
>                 Key: COUCHDB-87
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-87
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 0.8
>            Reporter: David Reid
>
> Transfer-Encoding: chunked is only specified in HTTP/1.1 making it incorrect to send
it to a client who advertises themselves as HTTP/1.0.
> This currently causes Paisley which is an HTTP/1.0 client to hang waiting for CouchDB
to sever the connection.  Which may indicate that CouchDB is also trying to use a persistent
connection by default which is also not allowed in HTTP/1.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message