[
https://issues.apache.org/jira/browse/COUCHDB-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778142#action_12778142
]
Paul Joseph Davis commented on COUCHDB-558:
-------------------------------------------
Oh my bad, I haven't had my required intake of chemicals to think clearly, but
I don't think this going to be completely doable directly in
mochiweb_request.erl. Which means that this might have to spider into the
individual handler functions.
Basically, I can't think of a good place where we differentiate between
attachment requests that are streamed to disk and requests that are buffered.
Preferably this patch would just work regardless, but I'm having a hard time to
come up with a method that wouldn't require putting guards on each handler
function which is obviously less than ideal.
> Validate Content-MD5 request headers on uploads
> -----------------------------------------------
>
> Key: COUCHDB-558
> URL: https://issues.apache.org/jira/browse/COUCHDB-558
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core, HTTP Interface
> Reporter: Adam Kocoloski
> Fix For: 0.11
>
> Attachments: jira-couchdb-558-for-trunk-2nd-try.patch,
> jira-couchdb-558-for-trunk-3rd-try.patch, jira-couchdb-558-for-trunk.patch
>
>
> We could detect in-flight data corruption if a client sends a Content-MD5
> header along with the data and Couch validates the MD5 on arrival.
> RFC1864 - The Content-MD5 Header Field
> http://www.faqs.org/rfcs/rfc1864.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
