In general a 302 redirect to the same exact resource should be
considered a software bug or something elese.
I do not think that squid needs as a proxy to handle these problems but
indeed a patch for that with a basic settings of "deny 302 cache that
reflect ot itself"
The same thing can be done by just not caching the 0-X range. or
explictly obey cache controls for these requests.
Eliezer
On 10/13/2013 08:15 PM, calode wrote:
Eliezer ,
you are absolutely right it matched refreshCheck: Matched '<none> 0 20%%
259200'
but I got a MISS/200 again : TCP_MISS/200 14169 GET
http://i1.ytimg.com/vi/pMr5W4bCP8s/mqdefault.jpg
I am not sure if you are getting MISS/304 on your side , and I didn't really
understand if you got anything
from the previous logs !? .
what do you mean (I have just seen something nice in the ETAG headers while
reading some
stuff. ) ? .
--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Help-Squid-3-4-0-2-ytimg-tp4662579p4662621.html
Sent from the Squid - Users mailing list archive at Nabble.com.
