- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 8 Apr 2009 16:39:46 +1000
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Cyrus Daboo <cyrus@daboo.name>, Lisa Dusseault <lisad@messagingarchitects.com>, ietf-http-wg@w3.org
I *think* this is tied up in #110 and #22... On 31/01/2009, at 3:39 AM, Julian Reschke wrote: > Cyrus Daboo wrote: >> - In the example in Section 2.1 there is a Content-MD5 header in >> the response. What does that refer to? The actual response body is >> empty. > > Right. This contradicts the definition of Content-MD5 (<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.14.15 > >), so it probably would be good to remove it. > > That being said: I think the HTTPbis definition of Content-MD5 > should be changed so that it can be sent with a 204 as updated > metadata. (new issue?) -- Mark Nottingham http://www.mnot.net/
Received on Wednesday, 8 April 2009 06:40:24 UTC