Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
The only users of #cache[expire]
in all of Drupal core is BlockViewBuilder
.
We currently have both #cache[max-age]
and #cache[expire]
. max-age
bubbles, expire
doesn't.
max-age
matches HTTP terminology & semantics. expire
doesn't (in HTTP 1.0, there's expires
, note the additional 's', which all best practices recommend against in favor of max-age
).
Proposed resolution
Remove it.
Remaining tasks
None.
User interface changes
None.
API changes
Removed #cache[expire]
, use #cache[max-age]
instead.
Comment | File | Size | Author |
---|---|---|---|
#1 | render_cache_expire-2458993-1.patch | 4.52 KB | Wim Leers |
Comments
Comment #1
Wim LeersComment #2
Fabianx CreditAttribution: Fabianx for Drupal Association commentedRTBC, looks good to me.
Comment #3
catchYep straightforward dead code removal.
Committed/pushed to 8.0.x, thanks!