Looking at the RFC at:
---
http://www.faqs.org/rfcs/rfc2616.html
and specifically section 14.27 which covers If-Range, it looks
like Cherokee is in fact doing the wrong thing. From the RFC:
---
If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
If the entity tag given in the If-Range header matches the
current entity tag for the entity, then the server SHOULD provide
the specified sub-range of the entity using a 206 (Partial
content) response. If the entity tag does not match, then the
server SHOULD return the entire entity using a 200 (OK) response.
---
Since APT passes:
---
If-Range: Sat, 29 Oct 2005 20:11:16 GMT
and Cherokee replies:
---
Last-Modified: Sun, 30 Oct 2005 21:11:50 GMT
Cherokee should have replied with a 200 instead of a 206 since
the If-Range and Last-Modified do not match.
I also just realized I cut the wrong portions of the
Apache conversation out of the original debug file. I'm
attaching the completely correct file just in case anyone
actually wants to reference it.
--
Mark Nipper e-contacts:
832 Tanglewood Drive [EMAIL PROTECTED]
Bryan, Texas 77802-4013 http://nipsy.bitgnome.net/
(979)575-3193 AIM/Yahoo: texasnipsy ICQ: 66971617
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
Light travels faster than sound. This is why some people appear
bright until you hear them speak.
----end random quote of the moment----
GET /debian/dists/unstable/Release.gpg HTTP/1.1
Host: mirror.tamu.edu
Connection: keep-alive
Range: bytes=188-
If-Range: Sat, 29 Oct 2005 20:11:16 GMT
User-Agent: Debian APT-HTTP/1.3
Get:1 http://mirror.tamu.edu unstable Release.gpg [189B]
HTTP/1.1 206 Partial Content
Connection: Keep-Alive
Keep-Alive: timeout=15
Date: Mon, 31 Oct 2005 07:46:13 GMT
Server: Cherokee
Content-Range: bytes 188-188/189
Content-Length: 1
Etag: 43653718=bd
Last-Modified: Sun, 30 Oct 2005 21:11:52 GMT
GET /debian/dists/unstable/Release.gpg HTTP/1.1
Host: http.us.debian.org
Connection: keep-alive
Range: bytes=188-
If-Range: Sat, 29 Oct 2005 20:11:16 GMT
User-Agent: Debian APT-HTTP/1.3
Get:7 http://http.us.debian.org unstable Release.gpg [189B]
HTTP/1.1 200 OK
Date: Mon, 31 Oct 2005 07:46:13 GMT
Server: Apache/1.3.33 (Debian GNU/Linux)
Last-Modified: Sun, 30 Oct 2005 21:11:52 GMT
ETag: "20e401e-bd-43653718"
Accept-Ranges: bytes
Content-Length: 189
Keep-Alive: timeout=15, max=99
Connection: Keep-Alive
Content-Type: text/plain; charset=iso-8859-1
W: GPG error: http://mirror.tamu.edu unstable Release: The following signatures
were invalid: BADSIG F1D53D8C4F368D5D Debian Archive Automatic Signing Key
(2005) <[EMAIL PROTECTED]>
W: GPG error: http://mirror.tamu.edu experimental Release: The following
signatures were invalid: BADSIG F1D53D8C4F368D5D Debian Archive Automatic
Signing Key (2005) <[EMAIL PROTECTED]>
W: You may want to run apt-get update to correct these problems
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
