[ https://issues.apache.org/jira/browse/COUCHDB-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772694#action_12772694 ]
Adam Kocoloski commented on COUCHDB-558: ---------------------------------------- Bah, what a shame. I think we ought to go ahead and implement Content-MD5 anyway -- we can always add other algorithms in addition to it. And I believe you're right, sha1 is the only other choice in the crypto module. > 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.