[
https://issues.apache.org/jira/browse/COUCHDB-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743047#action_12743047
]
Paul Joseph Davis commented on COUCHDB-461:
-------------------------------------------
Benoit, can you comment on how CouchDB is currently breaking the HTTP spec so
we have a record of it? IIRC, it was something that we would expect chunked
transfers by default instead of rejecting them but I'd like to have the reason
written down.
Also, I'd suggest that for attachments we don't use chunked transfers because
we should never need it. Unless someone can give me a use case that absolutely
requires receiving chunked attachments I'd vote to remove them and use a
straight up Content-Lenght.
> attachments - handle correctly chunked encoding and Content-Length, send
> attachments unchunked
> ----------------------------------------------------------------------------------------------
>
> Key: COUCHDB-461
> URL: https://issues.apache.org/jira/browse/COUCHDB-461
> Project: CouchDB
> Issue Type: Bug
> Reporter: Benoit Chesneau
> Fix For: 0.10
>
> Attachments: attachments_get_length.diff,
> attachments_put_length.diff, chunked.diff, chunked2.diff
>
>
> This patch allow couchdb to send attachments unchunked, instead,
> Content-Length is fixed and content is streamed. It also fix attachments PUT
> by detecting first if encoding is chunked then test the length witch is the
> standard way to do it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
