- 🇬🇧United Kingdom catch
Don't think this makes sense, the contents of 404 pages are usually pretty cacheable, unless you're using search_404 or something but that can set its own max-age.
Follow-up from #2699613: Set a shorter TTL for 404 responses in page_cache module → .
We've added negative_ttl there, but so far only using it for the page cache.
There are two ways we could apply this:
1. Apply it indiscriminately to any cache item on a 404. This means something that's the same on non-404 pages would get cached for an unnecessarily short time though.
2. Apply it as cacheable metadata for the URL cache context, only on 404s, this would have mitigated #2699627: url.path cache context for breadcrumbs is unnecessarily granular → . The advantage of this is the per-url cache context definitely determines reliably between being on a 404 or not.
Closed: won't fix
11.0 🔥
render system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Don't think this makes sense, the contents of 404 pages are usually pretty cacheable, unless you're using search_404 or something but that can set its own max-age.