- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Fri, 29 Jul 2011 17:22:35 +1200
- To: ietf-http-wg@w3.org
On 29/07/11 12:22, Eric J. Bowman wrote: > Julian Reschke wrote: >> >>> >>> 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? >> > > Maybe just add "(deprecated)" there? Since its deprecated, does it stay untouchable by updated middleware or does it now fall under headers which can be stripped for efficiency? AYJ
Received on Friday, 29 July 2011 05:23:11 UTC