Ritter, Nicholas wrote:
Thanks Chris for the information you provided.
The application for which I am messing with is still not caching the jar
files though. I get TCP_MISS/200 messages now. I think it is because the
server is providing expiry information as you stated, this is the only
way which I can see it behaving in the manner depicted.
Although I can't believe I am asking this, is there a way to selectively
ignore server expiry information?
With a refresh pattern...
refresh_pattern -i ^http://expiry.example.com/.*\.jar(\?.*)? 480
20% 4320 ignore-no-cache ignore-no-store override-expire
override-lastmod
...but make sure that line is pretty high up; refresh patterns are
first-match. You might want to use wget, squidclient or the Live HTTP
Headers plugin for Firefox to verify the headers the server is sending
back. The cacheability engine is another useful tool.
Using the above refresh pattern is going to have some effect on the
maximum amount of traffic your Squid will be able to handle. It's a
fairly complex test that has to be performed on every (non-cached?)
request. Obviously the better option would be to fix the expiry headers
on the origin server, if possible.
Nick
Chris
