#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 timgraham):
I'm not sure if the proposed behavior is correct. From
[https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3 RC2616
sec14.9.3] (which I only skimmed, so please provide another reference if
it's wrong):
If a response includes both an Expires header and a max-age directive,
the max-age directive overrides the Expires header, even if the Expires
header is more restrictive.
I think I understand the idea behind the
[https://github.com/django/django/pull/7246 PR], however, it seems to
treat the Expires as authoritative rather than max-age.
--
Ticket URL: <https://code.djangoproject.com/ticket/27225#comment:2>
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.901fb23862db4ad524e7a90d0c34779d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
