#27225: Cache-Control's max-age doesn't match Expires for responses taken from
cache
-------------------------------+--------------------------------------
Reporter: renskiy | Owner: renskiy
Type: Bug | Status: assigned
Component: HTTP handling | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by renskiy):
[RFC7234](https://tools.ietf.org/html/rfc7234#section-5.1) says about
'''Age''' header which indicates age of the cache, so instead of Cache-
Control's max-age regeneration it is possible to set Age. Also there is
good visual explanation how browser cache should work:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching#Freshness
--
Ticket URL: <https://code.djangoproject.com/ticket/27225#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.5c5481f3e11a481ba13a7102027d28f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
