> Hi everybody,
> for my web-application (it must currently work only under IE6) I have
[quoted text clipped - 25 lines]
> Thank you very much for your suggestions :-)
> John
I'm guessing that what's going in is that the browser is loading a
cached back page, so it goes back to the cached page and sends no
request to the servlet. If this is the case, then sending a simple AJAX
request using a window.onload handler to get the servlet to recognize
the back should be sufficient.
Randy Webb - 12 Apr 2007 04:33 GMT
Joshua Cranmer said the following on 4/11/2007 10:43 PM:
>> Hi everybody,
>> for my web-application (it must currently work only under IE6) I have
[quoted text clipped - 31 lines]
> request using a window.onload handler to get the servlet to recognize
> the back should be sufficient.
That won't work as the onload event isn't always fire when the page is
retrieved from the cache.

Signature
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Adam Maass - 12 Apr 2007 05:08 GMT
>> Hi everybody,
>> for my web-application (it must currently work only under IE6) I have
[quoted text clipped - 31 lines]
> window.onload handler to get the servlet to recognize the back should be
> sufficient.
Nocache HTTP response headers. I forget the exact format, but that should do
the trick.
Sanjay - 12 Apr 2007 13:25 GMT
> Nocache HTTP response headers. I forget the exact format, but that
> should do the trick.
If I remember correctly, this won't work in Firefox, as it has some kind
of cache (called back-forward cache?). Firefox caches pages even if you
set no-cache in http headers.