Re: Squid3 ranges

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Fri, 6 Jan 2006 16:57:44 +0100 (CET)

On Fri, 6 Jan 2006, Gonzalo Arana wrote:

> I've come across a request/response like this:
>
>
> GET http://some-host/some-path HTTP/1.0
> Accept: */*
> User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98)
> Host: 212.68.148.119
> Range: bytes=3927657-4893707
> Cache-Control: max-age=259200
>
> HTTP/1.1 206 Partial Content
> Server: Microsoft-IIS/5.0
> Connection: keep-alive
> Date: Wed, 04 Jan 2006 03:21:00 GMT
> Content-Type: video/x-msvideo
> Last-Modified: Fri, 30 Dec 2005 19:18:04 GMT
> ETag: "101c26c275dc61:93f"
> Content-Length: 894247
> Content-Range: bytes 6818521-7712767/7712768

Thats a interesting one.. returning a completely different range than
requested. Not forbidden, but quite odd thing to do. I wonder what the
clients thinks about this..

> Which triggered the assertion failure detailed in bug# 624.
>
> Any hints on how squid should handle this bizarre response?
> Just forward the reply "as is", return a 409 response, or something else?

Forward as-is in my opinion.

Regards
Henrik
Received on Fri Jan 06 2006 - 08:57:48 MST

This archive was generated by hypermail pre-2.1.9 : Fri Jan 27 2006 - 12:00:02 MST