> IE and Tomcat are both running on my machine, there certainly are no
> proxies or firewalls involved.
>
> I know IE is caching because the back button works even after shutting
> Tomcat down.
Ah, the BACK button.
Read RFC 2616 which describes HTTP/1.1 and caching and the BACK button.
After discussing caching extensively, there is this short section. You and
many other people will find this section useful:
13.13 History Lists
User agents often have history mechanisms, such as "Back" buttons and
history lists, which can be used to redisplay an entity retrieved
earlier in a session.
History mechanisms and caches are different. In particular history
mechanisms SHOULD NOT try to show a semantically transparent view of
the current state of a resource. Rather, a history mechanism is meant
to show exactly what the user saw at the time when the resource was
retrieved.
By default, an expiration time does not apply to history mechanisms.
If the entity is still in storage, a history mechanism SHOULD display
it even if the entity has expired, unless the user has specifically
configured the agent to refresh expired history documents.
The BACK button SHOULD show the cached version, and that is just what IE
does.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
