From: Hubert Grzeskowiak <linux-admin-ml@nemesis13.de>
To: linux-admin@vger.kernel.org
Subject: Re: apache 2 expiresdefault
Date: Wed, 09 Jul 2008 06:17:10 +0200 [thread overview]
Message-ID: <48743BC6.6090807@nemesis13.de> (raw)
In-Reply-To: <18548.11759.634428.311199@cerise.gclements.plus.com>
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.
next prev parent reply other threads:[~2008-07-09 4:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 21:09 apache 2 expiresdefault Jake Ravenwood
2008-07-09 3:18 ` Glynn Clements
2008-07-09 4:17 ` Hubert Grzeskowiak [this message]
2008-07-09 17:02 ` Jake Ravenwood
2008-07-09 20:59 ` Glynn Clements
[not found] <8CAB003ECFFDA63-1344-1D19@WEBMAIL-DC15.sysops.aol.com>
2008-07-09 19:04 ` Jake Ravenwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48743BC6.6090807@nemesis13.de \
--to=linux-admin-ml@nemesis13.de \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).