hi aiko, On Sat, Jan 04, 2014 at 06:02:22PM +0100, Aiko Barz wrote: > Example file size: 380476 > Requested range by zsync: bytes=0-380927 > > So, the client asked for a part of the file that lies beyond the end > of the file. Most web servers ignore this behavior like nginx: > > Request: > GET /20121009-165404.jpg HTTP/1.1 > User-Agent: zsync/0.6.2 > Host: tumbleweed:80 > Referer: http://tumbleweed:80/20121009-165404.jpg.zsync > Range: bytes=0-380927 > Connection: close > > Reply: > HTTP/1.1 206 Partial Content > Server: nginx/1.2.1 > Date: Sat, 04 Jan 2014 15:44:01 GMT > Content-Type: image/jpeg > Content-Length: 380476 > Last-Modified: Fri, 03 Jan 2014 14:03:32 GMT > Connection: close > Content-Range: bytes 0-380475/380476 > > But from my understanding, this might also result in 416 reply: > 416 Requested Range Not Satisfiable
very interesting, but could you give me a little bit more information: - to rephrase, you are saying that zsync sends range requests past the end of the file, and that some/most webservers satisfy these by only returning the data until the end of file, but that it would also be spec-compliant to return an error. correct? - is this a theoretical thing or can you observe it on an actual file? could I have that file? - have you ever seen that error 416? thanks robert -- Robert Lemmen http://www.semistable.com
signature.asc
Description: Digital signature
