[
https://issues.apache.org/jira/browse/COUCHDB-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592825#action_12592825
]
Christopher Lenz commented on COUCHDB-40:
-----------------------------------------
Are you saying the response requires a Content-Length header to work with those
proxies? The change to MochiWeb does not set the content-length, because that
would require buffering in all those instances where we actually use chunking,
and that would suck.
Instead of the content-length, it relies on the server closing the connection
when the last piece of data has been sent. I don't see why that should not work
with proper HTTP/1.0 clients.
> Transfer-Encoding: Chunked on HTTP 1.0 request
> ----------------------------------------------
>
> Key: COUCHDB-40
> URL: https://issues.apache.org/jira/browse/COUCHDB-40
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Environment: Irrelevant
> Reporter: Kore Nordmann
> Attachments: compat_http10_couchdb_r649048.diff,
> mochiweb_chunking_http10.diff, patch-share_www_script_jquery_couch_js,
> patch-src_couchdb_couch_httpd_erl
>
>
> The following request:
> > DELETE /test HTTP/1.0
> > Host: localhost
> is responded like:
> > HTTP/1.0 404 Object Not Found
> > Transfer-Encoding: chunked
> > Server: MochiWeb/1.0 (Any of you quaids got a smint?)
> > Date: Tue, 15 Apr 2008 20:39:07 GMT
> > Content-Type: text/plain;charset=utf-8
> >
> > 28
> > {"error":"not_found","reason":"missing"}
> > 0
> while chunked transfer-encoding is only supported by HTTP 1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
