[
https://issues.apache.org/jira/browse/COUCHDB-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772725#action_12772725
]
Robert Newson commented on COUCHDB-558:
---------------------------------------
MD5 is fine for guarding against transmission errors and checking against
corruption. That is, the current uses are just fine, imo. I do expect to have
to convince my PHB that using MD5 is fine (we currently use SHA256 for
essentially the same thing), but that's my sorrow, not yours. :)
IIRC, I believe S3 uses this header (and therefore MD5) for the same purpose.
> 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
>
>
> 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.
