I have trying out the No Cache and Expires but no work

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: I have trying out the No Cache and Expires but no work by tinman (Curate) on Jun 07, 2001 at 07:43 UTC
For a really good site that deals with the issues that you have, try Web Caching. I would probably tell you to use the tools on that site to check if your cache control headers are compliant... Some browsers, unfortunately, choose to ignore certain headers (as do some proxy servers).. so it may not be a content but rather a browser issue... One thing: I'm not sure if the Expires header is valid... see here for more details.. HTH	[reply]
Re: Re: I have trying out the No Cache and Expires but no work by tachyon (Chancellor) on Jun 07, 2001 at 16:10 UTC
Good post. The expires header requires a valid date if you output it yourself ie: Expires: Fri, 30 Oct 1998 14:19:41 GMT With CGI.pm however, a variety of options (including -'1d')are allowed when you pass values to it, presumably these are converted into a time in GMT - I have never bothered to check. If you send invalid date values in an HTTP expires header (ie 'now' or '0') it is interpreted as being in the past so has the desired effect anyway. tachyon	[reply]
Re: I have trying out the No Cache and Expires but no work by lestrrat (Deacon) on Jun 07, 2001 at 11:40 UTC
From what I know, at least Netscape ignores the expires header. HOWEVER, most HTTP caching program/appliances will honor the value That doesn't mean that the page will be reloaded if you have a proxy cache in between your browser and the server, for it's the browser that actually determines if it should verify with the server ( or the proxy cache ) if the content has expired The fail safe way is this: You need to use the META tag in the HTML, as in: `<head> <meta http-equiv="Expires" content="......."> .... </head>` [download] This will let major browsers know that the content will expire at some known time in the future, thus forcing the browser to reload At the same time, you should set the HTTP Expires header, so that if there is a proxy-cache in between the browser and the server, the contents are more likely to be renewed. Hope that helps P.S., of course, you still may want to telnet to your web server and make sure that it's spitting out the correct headers that you think it's spitting out...	[reply] [d/l]
Re: I have trying out the No Cache and Expires but no work by mattr (Curate) on Jun 07, 2001 at 10:46 UTC
Are you using Netscape? I have found that while Netscape for the most part honors cookie cancellation directives, Explorer does a very bad job of it. This could be a similar problem..	[reply]
Re: Re: I have trying out the No Cache and Expires but no work by Beatnik (Parson) on Jun 07, 2001 at 12:42 UTC
He means document expiring, not cookie expiring. AFAIK Internet Explorer s*cks at everything :) Greetz Beatnik ... Quidquid perl dictum sit, altum viditur.	[reply]
Re: I have trying out the No Cache and Expires but no work by Beatnik (Parson) on Jun 07, 2001 at 10:50 UTC
I doubt both `expires` as `no-cache` are guaranteed to work. Greetz Beatnik ... Quidquid perl dictum sit, altum viditur.	[reply] [d/l] [select]


Welcome to the Monastery
	PerlMonks