|
Ok but after enabling collapsed_forwarding, EVEN when disabling it again, the cache.log are full of clientProcessHit: Vary object loop! What happened ? My cache was modified ? collapsed is off now and
even after restarting squid I'm still getting a flood of these
messages which were not there before. About the acl with "range_list_path", I've already done that to test.. it really alleviates the problem but it's still there.
Best Regards, -- Heiler Bemerguy - (91) 98151-4894 Assessor Técnico - CINBESA (91) 3184-1751
Em 12/05/2016 20:21, joe escreveu:
do not worry about vary its not a bug its the way its setup the vary handling yet it need plenty of work this is my guess after i look at the code for a range_offset_limit use this test im using it long time and its wonderful collapsed_forwarding on acl range_list_path urlpath_regex \.(mar|msp|esd|pkg\?) range_offset_limit -1 windows_list_path range_offset_limit 16 KB all !range_list_path #<---if you need this quick_abort_min 0 KB quick_abort_max 0 KB quick_abort_pct 100 im caching the above extension perfectly you can add to it -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Getting-the-full-file-content-on-a-range-request-but-not-on-EVERY-get-tp4677503p4677543.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
