Having searched on this issue, I realized that not all browsers
(or their versions) behave always as expected with these directives.
What I did to solve a similar problem was to subclass the
TemplateLink class and add some code to always add a dummy
path info variable so that the browser thinks that this is a different
url. Below is the code.
public class TemplateLinkEx extends TemplateLink {
public TemplateLinkEx() {
super();
}
public TemplateLinkEx(RunData data)
{
super(data);
addPathInfo("nocacheid", new java.util.Date().getTime());
}
}
I hope that helps.
Costas
----- Original Message -----
From: "Scott Eade" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 07, 2001 8:05 AM
Subject: Browser cache control
> Because the data changes all of the time, I need to instruct all
> browsers that surf to my turbine site to not use their cache nor
> any other cache that may be sitting in a proxy server between
> the browser and the web server. To do this I currently have:
>
> $page.setHttpEquiv("Cache-Control", "no-cache")
> $page.setHttpEquiv("Pragma", "no-cache")
>
> in my default page layout. This clearly adds:
>
> <meta content="no-cache" http-equiv="Cache-Control">
> <meta content="no-cache" http-equiv="Pragma">
>
> to the HTML output, but I am not sure if it is actually setting
> the HTTP headers - the behaviour I am seeing is that it is
> not.
>
> How can I set the actual HTTP headers so that the content
> expires immediately? Won't all template driven apps need
> to expire their content pretty much immediately?
>
> Thanks,
>
> Scott
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
