Mark Nipper wrote:

> 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.
> ------------------------------------------------------------------------
>
> GET /debian/dists/unstable/Release.gpg HTTP/1.1
> Range: bytes=188-
> If-Range: Sat, 29 Oct 2005 20:11:16 GMT
>
> Get:1 http://mirror.tamu.edu unstable Release.gpg [189B]
> HTTP/1.1 206 Partial Content
> Server: Cherokee
> Content-Range: bytes 188-188/189
> Content-Length: 1
> Last-Modified: Sun, 30 Oct 2005 21:11:52 GMT
> ------------------------------------------------------------------------

  Right, it was a bug.

  I have committed a patch, it is now in the SVN.  Now, Cherokee
  checks for the If-Range header; it swaps to a 200 error code and
  sends the full file content if needed.

  I have also added a new couple of QA tests to ensure it works:

  http://svn.0x50.org/file/cherokee/qa/105-If-Range.py
  http://svn.0x50.org/file/cherokee/qa/106-If-Range2.py


  Mark, thanks a million for the report! :-)

--
Greetings, alo.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee

Reply via email to