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 respon
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
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 b
t 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. Se
the new content!?!!?!?!!'.
DanO
> -Original Message-
> From: Bernard Durfee [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 09, 2001 1:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: IE Caching
>
>
> Craig,
> Everything is coming out of JSPs, so it must be IE
r 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
riday, February 09, 2001 5:09 PM
To: [EMAIL PROTECTED]
Subject: RE: IE Caching
i've had the same problems using tomcat, specifically with <@include>
directives in JSPs.
delete the classes in the /work directory and restart httpd.
should work fine, or at least it did for me when started tea
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 fir
> 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
Title: RE: IE Caching
Based on your previous response, I assume that when you say "caching content", you don't mean that the user is seeing old content, but that IE is dropping a copy of the file into its cache directory, even with caching turned off?
If so, then another s
> 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 d
Try this:
<%
response.setHeader("Pragma", "no-cache");
if( request.getProtocol().equals("HTTP/1.1") ) {
response.setHeader("Cache-Control", "no-cache");
}
%>
I hope it helps.
It worked for me.
Rick
-
To unsubscribe, e-mail
Try this:
<%
response.setHeader("Pragma", "no-cache");
if( request.getProtocol().equals("HTTP/1.1") ) {
response.setHeader("Cache-Control", "no-cache");
}
%>
I hope it helps.
It worked for me.
Rick
-
To unsubscribe, e-mail
Try this:
<%
response.setHeader("Pragma", "no-cache");
if( request.getProtocol().equals("HTTP/1.1") ) {
response.setHeader("Cache-Control", "no-cache");
}
%>
I hope it helps.
It worked for me.
Rick
-
To unsubscribe, e-mail:
iginal Message-
> From: Rick Roberts [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, February 09, 2001 10:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: IE Caching
>
> Try this:
>
> <%
> response.setHeader("Pragma", "no-cache");
> if( request.getP
> I think that the caching settings on IE only affect files
> written to disk.
You might try including something like this in the head section of the page's html:
It shouldn't make any difference if you've set the equivalent headers but 'should' and
'ie' don't really go together that well
I think that the caching settings on IE only affect files written to disk.
There appears to be a memory-only cache which stores the very latest stuff
which is not affected. This is what causes the problem, as clearly it will
contain whatever was the last page so pressing back shows the page witho
17 matches
Mail list logo