- From: Jamie Lokier <jamie@shareable.org>
- Date: Sun, 26 Jul 2009 19:56:14 +0100
- To: Henrik Nordstrom <henrik@henriknordstrom.net>
- Cc: "Roy T.Fielding" <fielding@gbiv.com>, HTTP Working Group <ietf-http-wg@w3.org>
Henrik Nordstrom wrote:
> - Squid indirectly implements it on the resource by implementing the
> requirements of 206 composing literally ("MUST include all of the
> entity-headers that would have been returned with a 200 (OK)") and not
> caring about Content-MD5 as the specs says it is not allowed to
> recompose it.
Indeed, if Squid simply didn't know about Content-MD5, it *couldn't*
toss it or change it.
If someone defines Content-SHA3 some day, caches will not modify or
discard that when combining or splitting partial responses - they'll
pass the header along unchanged.
-- Jamie
Received on Sunday, 26 July 2009 18:56:51 UTC