Hi jo, Pause. Breath. If I'm reading that long sentence right you are getting REFRESH_MODIFIED responses from servers with "new" content to be cached, which has not actually changed. What URL or URLs ? > > as i understand squid look at > file size > date expiery > +++ if the income header of the file never change why would squid see it as > TCP_REFRESH_MODIFIED > mmmmmm There are many things that might make a cached object need revalidation. Expires timestamp is just one of them. Having authentication credentials embeded in it is another. Private cookies attached, client happened to press force-reload button in their browser, etc. etc. Unfortunately in this case the server is responding with an entirely new object each time. Squid can't exactly prevent that happening. It is the server choosing what to send. If it is happening with a specific URL, or a few URLs the tool at redbot.org can say whether there is anything broken with the server responses that are causing problems. Otherwise a bit more detail about what your particular setup is will be needed to figure it out. What the proxy is intended to do / what its used for, how its connected to from clients, and the squid.conf. If you had any questions you want answers to in the rest of that text, please re-phrase them a bit more clearly and I will try to answer as best I can. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users