intercept ?? mostly those you see on accelerator that what i,m trying to explain in my other post i know the cause it's in varyEvaluateMatch in source code some how the vary its not empty and it might not match mem_obj->vary_headers so you end up in cache.log varyEvaluateMatch: Oops. Not a Vary match on second attempt and even if its public header dose same usually if its privet on Cache-Control dose that but it dose it on public as well i did some testing modifying the function i got excellent result but not the correct way its and old issue may be i was not posting the issue in correct way for the dev... to understand
-- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-5-16-and-vary-loop-objects-bug-tp4676901p4676904.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
