[
https://issues.apache.org/jira/browse/COUCHDB-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593185#action_12593185
]
Christopher Lenz commented on COUCHDB-40:
-----------------------------------------
The second patch has been accepted into the MochiWeb project, and has been
applied to the version in CouchDB trunk in r652206.
About adding a Content-Length header... there are many places (for example view
results) where we use start_json_response and Resp:write_chunk instead of just
send_json; those are the cases where we'd need to do buffering of the complete
response if we wanted to set the Content-Length appropriately. So I'm pretty
sure that's not a viable option unless we decide on doing response buffering,
which I personally don't think would be a good idea.
Waiting for some more feedback before resolving this. Also, I'd like some
details on why those JS changes are necessary. And links, specs, etc?
> 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, mochiweb_chunking_http10_2.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.
