Re: apache 2 expiresdefault

Glynn Clements wrote:
> Jake Ravenwood wrote:
> 
>> i have a linux/apache2 newly setup. i put it online last week but
>> after a day, i got a lot of email/phone complaints saying they are
>> seeing old pages/old contents of the site. My site changes
>> frequently(daily). after checking i found that apache has
>> ExpiresDefault A2419200 which spells to 28days. I changed it to
>> ExpiresDefault A0 and reload Apache. Some end-users are now seeing the
>> new content but some are still seeing the old pages. What else i
>> missed?
> 
> If someone already has a cached version with the 28-day expiry, their
> web browser (or an intermediate proxy) is likely to keep using it
> until it expires or until they force a reload. Nothing you do to your
> web server can force those existing copies to expire prematurely.
> 

hi Jake,
try adding those meta tags to your (x)html files (into the head part of 
course):

	<meta http-equiv="expires" content="-1">
	<meta http-equiv="pragma" content="no-cache">
	<meta http-equiv="cache-control" content="no-cache">

this won't force your clients to reload the page, but it should suppress 
future caching. it's just html, so sure not every browser will interpret 
that.
--
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html