Please don't top post (which is replying above the original message) - it makes the thread hard to follow. Diego Amadey wrote: > Adam Aube wrote: >> Diego Amadey wrote: >>> I have installed avgfree antivirus in the clients of my net, and i have >>> configured them to update their signatures using >>> my squid proxy (2.5Stable3) >>> They are working fine but the problem is that the update files (.bin) >>> are not being cached. >>> This is a part of the access.log. >>> 1106765778.379 27278 10.21.6.169 TCP_MISS/200 949270 GET >>> http://free.grisoft.cz/softw/70free/update/u7avi439u39282.bin - >>> DIRECT/193.86.3.37 application/octet-stream >> Can you show a few more TCP_MISS entries? AVG will attempt to do a custom >> download which will only include the updates that are needed rather than >> the entire definition file. It is possible that this custom download is >> different for each client, resulting in different URLs for each request. > I am sending a few more lines. The urls seems to be the same in some > requests, but the result is always a MISS. > 1106830838.756 14886 dsur503a.dsur TCP_MISS/200 176265 GET > http://free.grisoft.cz/softw/70free/update/u7avi440u433wk.bin - > DIRECT/193.86.3.36 application/octet-stream > 1106830897.456 371326 eco906b TCP_MISS/200 4204647 GET > http://free.grisoft.cz/softw/70free/update/u7avi440wk.bin - > DIRECT/193.86.3.37 application/octet-stream > 1106830903.492 28325 agri1049d.sagpya TCP_MISS/200 176265 GET > http://free.grisoft.cz/softw/70free/update/u7avi440u433wk.bin - > DIRECT/193.86.3.37 application/octet-stream These three entries show the actual content sent back to the clients (note the HTTP status code of 200). Only the first and third have the same URLs - the second entry is for a different URL. Based on your squid.conf and the access.log entries here, the third request should have been a TCP_HIT. It could be that the web server is sending a "Pragma: no-cache" HTTP header, causing Squid to not serve the request from the cache despite your refresh_pattern settings. Unfortunately, attemtping to test the URL with the Cacheability Test Engine results in a timeout, so I cannot verify this. AFAIK, there is no way to override "Pragma: no-cache" in Squid. If the server is indeed sending this header, then there is nothing you can do to force Squid to cache the update files. Adam