W3C home > Mailing lists > Public > www-validator@w3.org > May 2002

Re: W3C HTML Validator: Last Modified?

From: Harry Gibbens, Jr. <harryjr@deafworks.com>
Date: Tue, 07 May 2002 13:38:49 -0600
Message-Id: <3.0.6.32.20020507133849.007fb580@deafworks.com>
To: Nick Kew <nick@webthing.com>, Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: <www-validator@w3.org>
Hi all,

Here is the cache control meta tag ifnormation:

<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<META http-equiv="Content-Script-Type" content="type">
<META http-equiv="Content-Style-Type" content="text/css">
<META http-equiv="Expires" content="Tue, 01 Jan 2002 12:00:00 GMT">
<META http-equiv="Pragma" content="no-cache">
<META http-equiv="Cache-Control" content="no-cache">


Do they affect anything to do with the validator?

Thanks,
Harry Jr.



At 06:57 PM 5/7/2002 +0100, Nick Kew wrote:
>On Tue, 7 May 2002, Bjoern Hoehrmann wrote:
>
>> * Harry Gibbens, Jr. wrote:
>> >I updated a webpage and validate it.  But, the validator keeps a memory of
>> >an old webpage content (by looking at "Last Modified" line on the
>> >validator).  I hit "Revalidate" button, hoping that the validator updates
>> >its new Last Modified date.  No luck.
>
>Sounds like an over-aggressive cache.  Could be your browser or ISP.
>
>> Terje, do we send Cache-Control: no-cache and Pragma: no-cache?
>
>IMHO that would be wrong.  ISTM perfectly reasonable that the validator
>reports should be cacheable, and messing that up is going to annoy a
>lot of users.  OTOH, it might possibly help with some caches if the
>validator were to compute an Etag, and it could also set Last-Modified
>to that of the page being validated.
>
>-- 
>Nick Kew
>
>Available for contract work - Programming, Unix, Networking, Markup, etc.
>
>
>
Received on Tuesday, 7 May 2002 15:37:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:03 GMT