Re: Expiring CGI pages

I want to expire pages that my CGI sends to the browser.

I've had some luck (on some browsers) by also doing sending

 Cache-Control: no-cache
 Pragma: no-cache
[download]

The Cache-Control header is supposed to be a directive to caching proxies, but some browsers seem to honor it.

Comment on Re: Expiring CGI pages Download Code

Replies are listed 'Best First'.
Re: Re: Expiring CGI pages by legLess (Hermit) on Mar 07, 2002 at 20:42 UTC
Ok, fair enough. This does basically what I want, which is generate an "expired" warning in the browser. However, isn't it possible to actually run the script again? An in-between option? Not just showing the history page, and not just showing a warning, but actually having the page generated again for the user? (I think /. does this.) EDIT I should add that these pages are viewed only over a secure connection (HTTPS). -- man with no legs, inc.	[reply]
Re: Re: Re: Expiring CGI pages by seattlejohn (Deacon) on Mar 08, 2002 at 03:25 UTC
Take a look at this document for an in-depth explanation of caching behavior. I'm not sure /. actually behaves the way you imply. But the site's code is open source, so if you are really motivated you could figure out how they do it! ;-) My personal experience has been that caching behavior in browsers follows few rules and is a constant source of annoyances, but I wish you luck!!	[reply]