- From: Henrik Nordstrom <henrik@henriknordstrom.net>
- Date: Sat, 25 Jul 2009 16:45:10 +0200
- To: Yves Lafon <ylafon@w3.org>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
lör 2009-07-25 klockan 02:16 -0400 skrev Yves Lafon: > HEAD /Distrib/jigsaw_2.2.6.zip HTTP/1.1 > Host: jigsaw.w3.org > > HTTP/1.1 200 OK > Content-Md5: fBhlh9ttr14YAqe45Yi+xg== > Server: Jigsaw/2.3.0-beta1 > > ----- > > GET /Distrib/jigsaw_2.2.6.zip HTTP/1.1 > Host: jigsaw.w3.org > Range: bytes 0-1 > > HTTP/1.1 206 Partial Content > Content-Md5: 1xvdIsi7k7jSh9zm9GrtJQ== Crap, So then we definitely have conflicting implementations out there. Same response via a Squid cache which does not implement any bit of Content-MD5 calculation (and is not allowed to touch Content-MD5 by HTTP/1.1): GET http://jigsaw.w3.org/Distrib/jigsaw_2.2.6.zip HTTP/1.1 Range: bytes=0-1 HTTP/1.0 206 Partial Content Date: Sat, 25 Jul 2009 14:40:35 GMT Content-MD5: fBhlh9ttr14YAqe45Yi+xg== Content-Type: application/zip Expires: Thu, 30 Jul 2009 14:40:35 GMT Last-Modified: Tue, 10 Apr 2007 15:09:24 GMT Server: Jigsaw/2.3.0-beta1 Age: 126 X-Cache: HIT from henrik X-Cache-Lookup: HIT from henrik:3128 Via: 1.0 henrik (squid/3.HEAD-BZR) Proxy-Connection: close Content-Range: bytes 0-1/9331520 Content-Length: 2 Btw, the jigsaw server also does the following: GET /Distrib/jigsaw_2.2.6.zip HTTP/1.1 Host: jigsaw.w3.org Range: bytes=0-1 If-Range: "1k8cb5f:127e0lb8o" HTTP/1.1 206 Partial Content Cache-Control: max-age=432000 Date: Sat, 25 Jul 2009 08:58:59 GMT Content-Length: 2 Content-Md5: 1xvdIsi7k7jSh9zm9GrtJQ== Content-Range: bytes 0-1/9331520 Content-Type: application/zip Etag: "1k8cb5f:127e0lb8o" Expires: Thu, 30 Jul 2009 08:58:59 GMT Last-Modified: Tue, 10 Apr 2007 15:09:24 GMT Server: Jigsaw/2.3.0-beta1 which contradicts the SHOULD NOT on conditional requests... Regards Henrik
Received on Saturday, 25 July 2009 14:45:50 UTC