#17781: Django cache middleware does not set "Age" header as described in
rfc2616
-------------------------------------+--------------------
Reporter: corentin.chary@… | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: SVN
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+--------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/17781>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
