W3C home > Mailing lists > Public > public-bpwg@w3.org > June 2007

RE: The page is not served with a cache control header

From: Scheppe, Kai-Dietrich <k.scheppe@t-online.net>
Date: Mon, 25 Jun 2007 09:24:25 +0200
Message-ID: <398533C370C23441981074C456AA3BDD02141904@QEO00226.de.t-online.corp>
To: "alex. B." <lalou12@hotmail.com>, <public-bpwg@w3.org>


In addition to the comments you have already received, consider that the
http-equiv meta tag does not really work.
The idea is that the webserver reads the meta entries before the http
header and replaces the appropriate fields.
I have not heard of a webserver that actually does this.

Evidence is that the tester does not see a cache-control entry in your
http header => the webserver does not transfer the information into the

The best way is to check your HTTP Headers and then ask you ISP if
missing items can be updated.

You might find some useful information here:


-- Kai

> -----Original Message-----
> From: public-bpwg-request@w3.org 
> [mailto:public-bpwg-request@w3.org] On Behalf Of alex. B.
> Sent: Thursday, June 21, 2007 2:42 PM
> To: public-bpwg@w3.org
> Subject: The page is not served with a cache control header
> Hello,
> I have this error in my mobile's page :
> The page is not served with a cache control header.
> This test is related to the following Best Practices: CACHING 
> (techniques)
> I don't understand this error.  Could you help me?
> I try with some different meta but it's always the same error.Why???
> for exemple :
> <meta http-equiv="cache-control" content="max-age=100" />
> I look forward to your answer.
> A.B
> _________________________________________________________________
> Personnalisez votre Messenger avec Live.com 
> http://www.windowslive.fr/livecom/
Received on Monday, 25 June 2007 07:24:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:56 UTC