> Which quite likely triggers confusion within Squid as the store/object > interface is range aware. Has been issues there in the past, and quite > likely is more issues.. Is squid 2.7 Content-Range aware? Since these requests work in 2.7, is 2.7 just ignoring the range requests? -----Original Message----- From: Henrik Nordström [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Thursday, April 08, 2010 5:32 PM To: Amos Jeffries Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: Squid 3.1.1 and flash video scrubbing tor 2010-04-08 klockan 20:43 +1200 skrev Amos Jeffries: > FWIW, the flash player and the server are somewhat broken and playing > bad games with HTTP/1.1 Range requests. Which quite likely triggers confusion within Squid as the store/object interface is range aware. Has been issues there in the past, and quite likely is more issues.. Not 100% sure that response is technically broken, but it surely is an odd response. > It claims to be cacheable but isn't. Why isn't it? > If this "range" was merged into a > previous ranges of the object, or even fetched from the a full copy of > real object by any well behaved middleware proxy it would corrupt the > media transfer. We don't know how the server would react on requests for the same URI but with Range header.. There is no Content-Location header in the response, so merging of responses with different url parameters MUST NOT be done by any HTTP agent (including proxies). Content-aware merging of the data is allowed, but that's outside HTTP. Regards Henrik
