Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 62559 invoked from network); 15 Jan 2010 14:38:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jan 2010 14:38:25 -0000 Received: (qmail 33305 invoked by uid 500); 15 Jan 2010 14:38:25 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 33228 invoked by uid 500); 15 Jan 2010 14:38:25 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 33218 invoked by uid 99); 15 Jan 2010 14:38:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jan 2010 14:38:25 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jan 2010 14:38:14 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 74551234C498 for ; Fri, 15 Jan 2010 06:37:54 -0800 (PST) Message-ID: <989600343.264101263566274475.JavaMail.jira@brutus.apache.org> Date: Fri, 15 Jan 2010 14:37:54 +0000 (UTC) From: "Filipe Manana (JIRA)" To: dev@couchdb.apache.org Subject: [jira] Commented: (COUCHDB-558) Validate Content-MD5 request headers on uploads In-Reply-To: <82731282.1257191699494.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800713#action_12800713 ] Filipe Manana commented on COUCHDB-558: --------------------------------------- The mochiweb patch was merged on the 02 January 2010, revision 114, without any difference regarding the couch's version: http://code.google.com/p/mochiweb/source/diff?spec=svn114&r=114&format=side&path=/trunk/src/mochiweb_headers.erl :) > 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 > Assignee: Paul Joseph Davis > Fix For: 0.11 > > Attachments: jira-couchdb-558-10th-try-trunk.patch, jira-couchdb-558-4th-try.patch, jira-couchdb-558-5th-try.patch, jira-couchdb-558-6th-try-trunk.patch, jira-couchdb-558-7th-try-trunk.patch, jira-couchdb-558-8th-try-trunk.patch, jira-couchdb-558-9th-try-trunk.patch, jira-couchdb-558-for-trunk-2nd-try.patch, jira-couchdb-558-for-trunk-3rd-try.patch, jira-couchdb-558-for-trunk.patch, run.tpl.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.