>I think the client has just disabled caching for the relevant server.
>I would agree that in an ideal setup, the webserver should be responsible for
>maintaining >'freshness'. I suspect that there is a configuration gotcha with Portal
>and Squid which is >causing this problem, I am hoping someone else has hit this.
Ok, but basically squid doesn't know anything about or even knows what a Portal
is : it only looks at http headers for each acquired object for making relevant
caching decisions. These can also be verified with , for instance :
http://www.ircache.net/cgi-bin/cacheability.py
M.
