Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 92753 invoked from network); 30 Jun 2009 04:17:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Jun 2009 04:17:45 -0000 Received: (qmail 35930 invoked by uid 500); 30 Jun 2009 04:17:55 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 35871 invoked by uid 500); 30 Jun 2009 04:17:54 -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 35861 invoked by uid 99); 30 Jun 2009 04:17:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2009 04:17:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [80.68.94.123] (HELO tumbolia.org) (80.68.94.123) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2009 04:17:43 +0000 Received: from nslater by tumbolia.org with local (Exim 4.69) (envelope-from ) id 1MLUmZ-0007oR-3R for dev@couchdb.apache.org; Tue, 30 Jun 2009 05:17:23 +0100 Date: Tue, 30 Jun 2009 05:17:23 +0100 From: Noah Slater To: dev@couchdb.apache.org Subject: Re: Unicode normalization (was Re: The 1.0 Thread) Message-ID: <20090630041723.GA29683@tumbolia.org> Mail-Followup-To: dev@couchdb.apache.org References: <418F2A99-DC59-4BF3-B371-A2E07FD2C567@apache.org> <7db9abd30906252232o43fa92c8p2e455555024bec51@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Noah: Awesome User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Jun 26, 2009 at 07:08:32AM -0400, Damien Katz wrote: > Md5 here is for integrity purposes, not security, so manufactured > collisions aren't a problem we are worried about. And I don't think > there is standard SHA1 header, not that I could find anyway. I've been seeing some unrelated emails go past on the W3C HTTP WG mailing list about Content-MD5 header which reminded me of this thread. It seems that this value must be calculated from the MIME canonical response body, which means a different value for content ranges. This presumably means that CouchDB must refuse content range requests, send an MD5 value that does not match the document revision, or break RFC 1864. Best, -- Noah Slater, http://tumbolia.org/nslater