posted 19 years ago
Hmm, I know that if the browser is set to cache everything and only check for new content with a new browser instance, it is possible to set headers to make sure a page or a file is never cached (of course the browser has to recognize the headers, but it works with IE and Firefox). But is it possible to do the opposite - to force the browser to cache a resource even if the settings are "check for new content every visit to the page."
For example, if I have the same image displayed hundreds of times on a page, I don't care what the browser settings are - I don't want hundreds of requests for that image coming to my server from the same client.
-Yuriy