Re: W3C HTML Validator: Last Modified?

Hi all,


Last week I can't validate my pages.  Now, I can.   It seems that I must
wait for few days for the validator to erase its own memory cache so that
it can look into my pages as fresh contents.

I am now jumpy very happy with all of my pages which those passed by the

I will leave you guys to baffle why the valdator didn't work to refresh the
cache on my pages last week, but works great today.  I haven't changed or
untouched anything on those page contents.  

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 Thursday, 9 May 2002 10:20:20 UTC