- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 28 Jul 2011 22:51:39 +0200
- To: "Eric J. Bowman" <eric@bisonsystems.net>
- CC: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
On 2011-07-28 20:11, Eric J. Bowman wrote: > Mark Nottingham wrote: >> >> An alternate approach would be to deprecate the Content-MD5 header >> itself, since MD5 is deprecated, other signature mechanisms are being >> worked on, and the conflicting interpretations of this header make >> interop difficult. >> > > There are a couple references to Content-MD5 remaining, which is > confusing now that no Content-MD5 section exists; I suggest removing > mention of Content-MD5 from the following, perhaps making a note or two > in the "changes from RFC 2616" sections: p1 7.1.3.2, p2 7.4. P1: not sure - this is about non-modifiable headers. Does deprecating C-MD5 change this? P2: indeed. Best regards, Julian
Received on Thursday, 28 July 2011 20:52:27 UTC