I have to say that I've never had this problem with IE 5.0.
Since it seems like this is very constant, here are a few things
from past discussions that might be pertinant:
* Is it possible for some form of network cache to exist between you
and the server? (Server outside of firewall/proxy and you behind is the
most likely configuration for this, but your headers should also prevent
these devices/machines from caching)
* Are you 100% sure that you are seeing caching and not some flaw in
your JSP? I only say this because several people in the past had attributed
caching problems to their own bugs and the discussions went on for several
days before the root problem came out.
* Try change your URLs a little each time. Either have a request
parameter that contains some field that changes each time (probably based
upon the time the request was made) or do something similar with PathInfo.
Randy
-----Original Message-----
From: Bernard Durfee [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 4:41 PM
To: [EMAIL PROTECTED]
Subject: Re: IE Caching
Craig,
Everything is coming out of JSPs, so it must be IE then. Setting IE to
'Check Everytime' works a little better, at least it won't show old
content, but it still caches no matter what. This is a security issue
and it's critical for me to find a solution.
SSL will be used soon, which I've been told helps. It's amazing that
Microsoft would drop the ball like this when such high security risks
are at stake.
Thanks,
Bernie Durfee
"Craig R. McClanahan" wrote:
>
> Bernard Durfee wrote:
>
> > All,
> > I've tried every solution that I can think of to prevent IE from
> > caching content. I've placed every 'no-cache' meta tag and response
> > element known to man, but IE 5.5 still caches content.
> > Does Tomcat 3.2.1 effect the response header when sending the response
> > back to the browser? I'm using Tomcat as the webserver, I just want to
> > be sure the problem lies in IE as opposed to Tomcat.
> >
>
> If Tomcat is serving static content, it automatically adds a
"Content-Type"
> header (based on the MIME type mappings you have defined) and a "Date"
> header (which the browser can use for subsequent "If-Modified-Since"
> requests (which is what will happen if you configure your browser to
"check
> every time").
>
> If Tomcat is serving dynamic content (i.e. the output from a servlet or
JSP
> page), it is totally up to your application to set the response headers.
>
> In no case does Tomcat cache the output itself.
>
> >
> > Thanks,
> > Bernie Durfee
> >
>
> Craig McClanahan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
