Internet explorer cache

Question

My applet throws version mismatch error when my server and client are not synchronous. e.g. Client of version 1.0 is used with server of version 1.1.
when I faced this problem I tried to clear my cache by using Java control panel.
But still I am facing the same problem.
When I checked in file view of IE (Tools->Internet > Options->General->Settings->View) many html files of different version are seen.
I restarted my machine still same problem is coming.
I am using IE version 6.0.2800.1106
This is IE cache problem. Has anybody faced this problem? Is there any way to avoid this.

Answer 1

Hi Luk,
I found a bit about this at http://searchsecurity.techtarget.com/tip/1,289483,sid14_gci1132800,00.html#
Amoungst other things it says...
HTTP 1.1 introduced a new class of HTTP headers -- cache-control response headers. By using these headers you can control how both browser
caches and proxies handle Web pages and ensure that sensitive documents are not cached. HTTP headers are generated and sent by the Web
server before the actual HTML content of a page, and are only seen by the browser and any intermediate caches.
The two key cache-control response headers are:
NO-CACHE: This directive tells the browser that it has to request the document from the server for validation every time before releasing a cached copy.
NO-STORE: This directive instructs remote and local, shared and non-shared caches not to store a copy of the document under any conditions.
Note that no-cache does actually allow a copy of the document to be stored whereas no-store prohibits it. As you might expect, Internet Explorer (IE)
and Mozilla browsers have different implementations of these cache-control directives.
Both browsers will cache a document requested over an HTTP connection that has the "no-cache" directive set. Mozilla will not cache any pages by
default over an HTTPS connection, whereas Internet Explorer will, unless the user has enabled the "Do not save encrypted pages to disk" option. A
Mozilla browser never stores documents set with the "no-store" directive, but Internet Explorer only fully follows this directive when the page is requested
over an HTTPS connection. So the only way of ensuring that your sensitive documents and pages are not cached without requiring your users to manually
set any IE options is to use the "no-store" directive over an HTTPS connection. All browsers supporting HTTP 1.1 will support this directive.
Cheers
Graham Robbo