I had to learn about this because I had a customer behind a proxy (I
believe MS-Proxy 2) that was yelling at me that I was not making changes
to the website, when actually, all she was seeing was the cached version
of it. I have had problems with AOL customers since AOL proxies there web
connections.
Well there are a couple of ways of doing it.
For apache, if you have mod_expire activated, you can use:
ExpiresActive on
ExpiresDefault "now plus 6 hour"
Also, check this in your config:
#
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with
each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line
disables
# this behavior, and proxies will be allowed to cache the documents.
#
#CacheNegotiatedDocs
This turns on expires. The now plus 6 hour expires things 6 hours from
now.
Perl with CGI.pm you can uses something like:
print header(-expires=>'+6h');
or
print header(-pragma=>'no-cache');
And this is out of the PHP manual using the header command:
header ("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); // Date in the past
header ("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT");
// always modified
header ("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1
header ("Pragma: no-cache"); // HTTP/1.0
On Sun, 27 Aug 2000, Chad W. Skinner wrote:
> Date: Sun, 27 Aug 2000 11:33:47 -0500
> From: Chad W. Skinner <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [OT] Expiring Web Pages
>
> Does anyone know why on some web pages when you click reload the server
> returns a page expired message. I would like to do a similar thing on my
> site, but if I tell the client not to cache the content it simply resubmits
> the information for a second time.
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
