You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Pernica, Jan" <pe...@dcb.cz> on 2001/06/11 09:09:03 UTC

RE: cache control problem in tomact 3.2.1

We use only tomcat and we set following:
            response.setHeader("Cache-Control", "no-cache"); 
            response.setHeader("Pragma", "no-cache"); 
            response.setDateHeader("max-age", 0); 
            response.setDateHeader("Expires", 0); 

and we combine it with:

                out.print("<META HTTP-EQUIV=\"Cache-Control\"
CONTENT=\"no-cache\">\n"); 
                out.print("<META HTTP-EQUIV=\"Pragma\"
CONTENT=\"no-cache\">\n"); 
                out.print("<META HTTP-EQUIV=\"max-age\" CONTENT=\"0\">\n"); 
                out.print("<META HTTP-EQUIV=\"Expires\" CONTENT=\"0\">\n"); 
 
it works fine for us

On Monday, June 11, 2001 9:23 AM, niraj@weblineindia.com
[SMTP:niraj@weblineindia.com] wrote:
> hi All
> 
> i have a global include file . i have put to header in the file as given
> below.
>     response.addHeader("Cache-Control","no-cache");
>     response.addHeader("expires","0");
> when i work with tomact + IIS    both header works fine.
> but when only tomact is running  the these headers doesn't work. is this
is
> the bug in tomact ?
> any solution please help.
> i am using WINNT and Tomact 3.2.1 and IIS 4.0
> thanks in advance.
> 
> niraj


__________________________________________________________________
Tato komunikace je urcena vyhradne pro adresata a je duverna. 
This communication is intended solely for the addressee and is confidential.