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

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

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

Comment on Re: I have trying out the No Cache and Expires but no work

Replies are listed 'Best First'.
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]

Replies are listed 'Best First'.

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]

In Section Seekers of Perl Wisdom