Opened 3 years ago

Closed 2 years ago

#17781 closed Bug (wontfix)

Django cache middleware does not set "Age" header as described in rfc2616

Reported by: corentin.chary@… Owned by: nobody
Component: Core (Cache system) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Django cache middleware set "Cache-Control: max-age=" and "Expires", but does not set "Age".
This can be an issue, because "max-age" in frozen, so you can only rely on "Expires" for expiration time. Having the "Age" header set would allow the client to now when this page was cached by django.

This feature would require adding a cache.age(key) function in all cache backends, which is far from trival, especially with backends such as memcached.

Change History (2)

comment:1 Changed 3 years ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design decision needed

comment:2 Changed 2 years ago by aaugustin

  • Resolution set to wontfix
  • Status changed from new to closed

No one besides the reporter expressed interest for this feature, there's no patch, and the description admits it's a lot of work with (as far as I can tell) mostly theoretical advantages.

I'm going to close the ticket, please make your case on django-developers (preferrably with a patch) if you want this feature request to be implemented.

Note: See TracTickets for help on using tickets.
Back to Top