couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Lenz (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 16:49:44 GMT

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

Christopher Lenz commented on COUCHDB-87:
-----------------------------------------

I can't reproduce this problem here:

$ telnet 127.0.0.1 5984
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET /blog/_all_docs?count=1 HTTP/1.0

HTTP/1.0 200 OK
Server: CouchDB/0.8.0-incubating (Erlang OTP/R12B)
Date: Fri, 27 Jun 2008 16:47:34 GMT
Content-Type: text/plain;charset=utf-8
Cache-Control: must-revalidate

{"total_rows":0,"offset":0,"rows":[
{"id":"0086A43F2BCCD05824A6EABD29EEE088","key":"0086A43F2BCCD05824A6EABD29EEE088","value":{"rev":"2239156694"}}
]}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