caching problems in IE6

[Allan Gaines]

Caching behavior in IE6

Our application experiences this problem when it runs in IE(not Netscape
or
Firefox).
The app consists of 2 frames - one frame has a submit button and box for

entering
a URL, the 2nd frame has a back button. The back button is implemented
in
javascript with window.history.go(-1). We download URLs from an(Apache)
server.
The back button works fine until the following: some of the pages we
download
have icons that when clicked, open a new window in the browser. After
this new
window is opened, when we hit the back button, instead of the previous
file
being retrieved from the browser cache, it is retrieved from our server.
We
know this because(among other things) we monitor our web traffic with a
sniffer. Its
as if, after we launch the extra window, the cache thinks that it does
not
have the
file that we are trying to retrieve, and gets it from the server. The
file
IS still in
the cache(we are using CacheMonitor). Does anyone have any ideas about
why
this is happening? Thank you.

 

[Robert Aldwinckle]

Caching behavior in IE6

Our application experiences this problem when it runs in IE(not Netscape
or
Firefox).
The app consists of 2 frames - one frame has a submit button and box for

entering
a URL, the 2nd frame has a back button. The back button is implemented
in
javascript with window.history.go(-1). We download URLs from an(Apache)
server.
The back button works fine until the following: some of the pages we
download
have icons that when clicked, open a new window in the browser. After
this new
window is opened, when we hit the back button, instead of the previous
file
being retrieved from the browser cache, it is retrieved from our server.
We
know this because(among other things) we monitor our web traffic with a
sniffer. Its
as if, after we launch the extra window, the cache thinks that it does
not
have the
file that we are trying to retrieve, and gets it from the server. The
file
IS still in
the cache(we are using CacheMonitor). Does anyone have any ideas about
why
this is happening? Thank you.

I have found that the only reliable way to go *only* to the cache
is to first set Work Offline otherwise there is always the possibility
that IE will at least send a check request for the page you are going
back to first.

If you want to stay in a Working Online state instead you could try
changing your cache-checking option to Never. (Alt-T,O,Alt-S,N)
However, then users are required to use the Refresh command
any time they suspect there might be fresher content. They can
minimize the need of that of course by always clearing their TIF;
e.g. either automatically or manually.


HTH

Robert Aldwinckle
---