On Wed, Dec 15, 2004 at 01:59:46PM +0100, Elsen Marc wrote: > > > > > > How do I force Squid to serve cached pages? > > > > It did manage to cache a page, but then ignored it. > > > > Running wget -S http://localhost/ a number of times I get this in my > > access.log:- > > > > 1103112862.880 80 127.0.0.1 TCP_MISS/200 3325 GET > >http://localhost:8080/ - DIRECT/127.0.0.1 text/html > >1103112897.320 140 127.0.0.1 TCP_REFRESH_MISS/200 3324 GET > >http://localhost:8080/ - >DIRECT/127.0.0.1 text/html > >1103114187.780 30 127.0.0.1 TCP_REFRESH_MISS/200 3324 GET > >http://localhost:8080/ - > >DIRECT/127.0.0.1 text/html > > > >The page is in Squid's cache, but as I understand the entries above, it is > >being ignored. Is this because of a Squid setting, or because there is > >something in the web preventing it from being served from cache? > > Hm, > > % wget -S > > -S means prints 'server response' ; this probably causes > squid to re-validate the object, as a result of the wget request headers. > > Check if it work, if '-S' is not used.
This is what I get when running wget http://localhost/ :- 1103115775.430 200 127.0.0.1 TCP_MISS/200 3325 GET http://localhost:8080/ - DIRECT/127.0.0.1 text/html I did restart Squid after clearing the cache to get this, but the page was again copied to the cache. I also got this entry in the cache.log although I don't know if it is related:- 2004/12/15 13:02:32| storeLateRelease: released 0 objects 2004/12/15 13:02:55| icmpRecv: recv: (61) Connection refused 2004/12/15 13:02:55| Closing Pinger socket on FD 15 > M. -- John
