W3C home > Mailing lists > Public > site-comments@w3.org > October 2017

Re: Stale 404 cache on lists.w3.org

From: Coralie Mercier <coralie@w3.org>
Date: Thu, 19 Oct 2017 21:21:54 +0200
Cc: "site-comments@w3.org" <site-comments@w3.org>
Message-Id: <F55D4851-A50A-4EF8-B89F-433C209800B1@w3.org>
To: Stian Soiland-Reyes <soiland-reyes@manchester.ac.uk>
Hello,

I apologise for not replying earlier. 
We kicked the cache yesterday further to your report and I misunderstood that our systeams team had gotten back to you to let you know. 

Glad you eventually found out it is now sorted out.

Kind regards,
Coralie

> On 19 Oct 2017, at 16:13 , Stian Soiland-Reyes <soiland-reyes@manchester.ac.uk> wrote:
> 
> The caches seems to have sorted themselves out today and my link works again.
>  
> Never mind then (except for that potential of temporary denial of service); thanks if anyone helped! 😊
>  
> -- 
> Stian Soiland-Reyes, eScience Lab
> School of Computer Science, The University of Manchester
> http://orcid.org/0000-0001-9842-9718
>  
> From: Stian Soiland-Reyes
> Sent: 17 October 2017 13:19
> To: site-comments@w3.org
> Subject: Stale 404 cache on lists.w3.org
>  
> Hi,
>  
> I did the mistake of trying to link to (my own email from https://lists.w3.org/Archives/Public/public-scholarlyhtml/2017Oct/ by guessing the URL before it was listed, but now
>  
> https://lists.w3.org/Archives/Public/public-scholarlyhtml/2017Oct/0002.html returns wrongly “404 Not Found” and with cache headers
>  
> Etag: "72vu9g:1b6ra1nf8"
> Expires: Fri, 12 Oct 2018 11:11:29 GMT
> Last-Modified: Thu, 19 Jan 2017 12:08:34 GMT
>  
> Does this mean my email message (which was available from 11:11:51 GMT)  will be 404 for 12 months?
>  
>  
> Testing with curl from a different machine on a different network gives same 404, http vs https the same.
>  
>  
> Minting a slightly different URI like https://lists.w3.org/Archives/Public/public-scholarlyhtml/2017Oct/0002 or https://lists.w3.org/Archives/Public/public-scholarlyhtml/2017Oct/0002.html?foo however works, which gives:
>  
> < Etag: "1h3ak6r:1bsl0g2lo"
> < Expires: Fri, 12 Oct 2018 11:12:28 GMT
> < Last-Modified: Tue, 17 Oct 2017 11:11:51 GMT
> < Server: Jigsaw/2.3.0-beta3
>  
>  
> But of course these URIs are not in the mailbox index. How can I expire the cached resource on the server side? 
>  
>  
> Even a Force-Refresh in Chrome or with curl -H "Cache-Control: no-cache" does not work, which seems to me to be a violation ofhttps://tools.ietf.org/html/rfc7234#section-4.2.4
>  
>  
> This also seems to me to imply that someone with evil intent and a little for-loop could falsely 404 all future emails on w3c mailing lists... but I guess the cache would be expelled earlier by reboots or so.
>  
> -- 
> Stian Soiland-Reyes, eScience Lab
> School of Computer Science, The University of Manchester
> http://orcid.org/0000-0001-9842-9718

--
Coralie Mercier  -  W3C Marketing & Communications -  https://www.w3.org
mailto:coralie@w3.org +337 810 795 22 https://www.w3.org/People/CMercier/
Received on Thursday, 19 October 2017 19:21:59 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 October 2017 19:22:07 UTC