Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • I've only checked the HNQ, I don't know if the other feeds have issues. Commented Apr 5, 2017 at 19:43
  • Guess it's the cache control max-age, which is set to, like... forever Commented Apr 5, 2017 at 19:51
  • @Cai It might interfere with normal browser requests, but curl, wget or just ctrl-f5 wouldn't care. They all fail right now. Commented Apr 6, 2017 at 7:38
  • well fwiw they're all updating for me (last-modified is always a within the last few minutes at least, I'm not actually checking the content...) Commented Apr 6, 2017 at 8:24
  • @Cai Are you sure? They're not for me. Can you check in a private session in your browser to make sure you're not logged in? Commented Apr 6, 2017 at 16:56
  • 1
    Both in a private session, definitely not logged in: HTTPS and HTTP, I've checked a couple times today and it seems to always been up to date Commented Apr 6, 2017 at 17:14
  • Actually, just noticed the max-age is looking a bit more reasonable on HTTPS now; I was getting the same as you on that earlier (although it was still up to date) Commented Apr 6, 2017 at 17:16
  • Yeh no idea, very strange... hopefully a dev will have a look and see what's going on Commented Apr 6, 2017 at 17:35
  • Thanks for the heads up, we're taking a look at the CDN here. Commented Apr 7, 2017 at 16:50
  • @isanae Just to help us save some dig time here - any idea when this started? You seem to be an avid user, so is this very recent? We haven't made any known changes here...so digging into the unknown. Commented Apr 7, 2017 at 17:14
  • @NickCraver I've opened a chat room. Commented Apr 7, 2017 at 17:16