On 24/11/18 6:28 am, Heiler Bemerguy wrote: > Hum, disabling that refresh_pattern and -k reconfigure seems to have > fixed it.. but.. why? > Something else is going on which is not visible in the details you have shown. - is the TCP connection containing a message pipeline? if so the data and FIN may be related to a previous response message in that pipeline. - are other refresh patterns being used (probably yes) ? - what are they? (before and after the change) - what did your cache.log have to say at the time of the connection termination? (may need debug level 2 or 5 enabled) Also, you were using override-* and ignore-* settings in that refresh_pattern that are not necessary for the Debian/Ubuntu servers. At best they will be doing nothing to these responses (ie ignore-no-store, ignore-private do nothing to Debian/Ubuntu responses). Some will be causing *worse* caching service from the proxy. override-lastmod with your small [84 day] expiry vastly reduces the _years_ these objects can actually be cached for, and prevents IMS revalidation being used to determine changes properly and store un-changed things longer. NP: Debian/Ubuntu official repositories do fully support IMS revalidation. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
