I'm not sure I understand why you can't append an arbritray
parameter to the end of the URLs. Just as long as IE has never seen that
exact URL before it shouldn't be able to think it can display a cached
version. Also, as long as your name is unusual, you should not mess up any
other processing (unexpected parameters would probably be ignored).
Another thought, though, could IE be somehow caching because its is
on the local machine? Basiclly IE seeing the URL if from Localhost and
makes some form of an arbritray decision that it won't load?
Randy
-----Original Message-----
From: Bernard Durfee [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 09, 2001 5:08 PM
To: [EMAIL PROTECTED]
Subject: Re: IE Caching
Randy,
In response to your suggestions...
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.
I've see the 'dynamic' URL solution before. The content on the page is
an aggregation of many different sources, thus appending the current
time to each link is not possible.
Thanks,
Bernie Durfee
Randy Layman wrote:
>
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
