From 264832f88e9acca3755545ccf391204cb56db72a Mon Sep 17 00:00:00 2001 From: Dominique Hazael-Massieux Date: Wed, 1 Jul 2020 09:56:47 +0200 Subject: [PATCH] Hande Last-Revised header in spec monitor the CSS draft servers uses a proprietary last-revised header which seems to give more useful information on the actual last modification of a spec, so we use it when it is available --- src/monitor-specs.js | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/monitor-specs.js b/src/monitor-specs.js index 1dc35d32..78485d46 100644 --- a/src/monitor-specs.js +++ b/src/monitor-specs.js @@ -19,8 +19,10 @@ const today = new Date().toJSON().slice(0, 10); Object.keys(monitorList.specs).map(s => {return {...monitorList.specs[s], url: s};})); for (let candidate of candidates) { await fetch(candidate.url).then(({headers}) => { - if (new Date(headers.get('Last-Modified')) > new Date(candidate.lastreviewed)) { - review_needed.push({...candidate, lastupdated: new Date(headers.get('Last-Modified')).toJSON()}); + // The CSS drafts use a proprietary header to expose the real last modification date + const lastRevised = headers.get('Last-Revised') ? new Date(headers.get('Last-Revised') : new Date(headers.get('Last-Modified'); + if (lastRevised > new Date(candidate.lastreviewed)) { + review_needed.push({...candidate, lastupdated: lastRevised.toJSON()}); } }); }