Link for Django 11/5 security release error

[profcommie]

I am getting a page not found error when trying to access https://www.djangoproject.com/weblog/2025/nov/05/security-releases/

[ulgens]

Just checked the page and it seems okay. Not sure what happened. @django/django-website Do we a cache layer that needs to be warmed?

[sarahboyce]

It's also possible that an email/forum post was sent out with this link before the blog post was published. Maybe @nessita might know if anything happened in this case?

[nessita]

It's also possible that an email/forum post was sent out with this link before the blog post was published. Maybe @nessita might know if anything happened in this case?

I'm pretty sure there is an issue with the website cache. I created the blogpost and visited it before publishing, while being logged in, because I wanted to review the draft but instead I got a 404 (that may be a separated issue). So, that response remained cached for the default cache period until it expired.

@django/django-website would it make sense to not cache 404 responses? 🤔

[ulgens]

I'm not even sure how/where we cache a 404 response. If that's the current case, +1 for disabling it.

[SaptakS]

I have created a separate issue to track the disabling of 404 cache response (and any other caching mechanism improvements). I think maybe we can close this issue now and track the caching improvements in the other issue if that makes sense.