[
https://issues.apache.org/jira/browse/COUCHDB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790763#action_12790763
]
Benoit Chesneau commented on COUCHDB-595:
-----------------------------------------
Testing here with a non chunked Transfer-Encoding and can't reproduce the
problem on latest trunk :
send: 'PUT /testdb/testingpurpose HTTP/1.1\r\nHost:
127.0.0.1:5984\r\nAccept-Encoding: identity\r\ncontent-length:
42\r\ncontent-type: application/octet-stream\r\nexpect:
100-continue\r\nuser-agent: restkit/0.9.2\r\n\r\n'
send: '{"essai": "ahah", "_id": "testingpurpose"}'
send: 'PUT /testdb/testingpurpose HTTP/1.1\r\nHost:
127.0.0.1:5984\r\nAccept-Encoding: identity\r\ncontent-length:
42\r\ncontent-type: application/octet-stream\r\nexpect:
100-continue\r\nuser-agent: restkit/0.9.2\r\n\r\n'
send: '{"essai": "ahah", "_id": "testingpurpose"}'
reply: 'HTTP/1.1 100 Continue\r\n'
reply: 'HTTP/1.1 409 Conflict\r\n'
header: Server: CouchDB/0.11.0bd3745d1e-git (Erlang OTP/R13B)
header: Date: Tue, 15 Dec 2009 14:43:51 GMT
header: Content-Type: text/plain;charset=utf-8
header: Content-Length: 58
header: Cache-Control: must-revalidate
> Expect/Continue support broken for non-chunked transfer uploads
> ---------------------------------------------------------------
>
> Key: COUCHDB-595
> URL: https://issues.apache.org/jira/browse/COUCHDB-595
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Robert Newson
>
> CouchDB does not send the "HTTP/1.1 100 CONTINUE\r\n" line in response to a
> request with header "Expect: 100-continue". It does do so for chunked
> transfer mode, so correct expect/continue behavior can be achieved by forcing
> chunked mode, even when the exact length of the body is known.
> mochiweb_request.erl's recv/1 method does not send the header, but
> stream_body/4 does.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
