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?

Nick

Reply via email to