#27211: Include HTTP-caching headers to "304 Not Modified" responses
-------------------------------+--------------------------------------
Reporter: renskiy | Owner: renskiy
Type: New feature | Status: new
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):
The server generating a 304 response MUST generate any of the
following header fields that would have been sent in a 200 (OK)
response to the same request: Cache-Control, Content-Location, Date,
ETag, Expires, and Vary.
Taken from RFC7232: [https://tools.ietf.org/html/rfc7232#section-4.1].
Usually responses with 200 code will include such headers (e.g. from views
decorated with cache_page), so according to the RFC responses with 304
code must also include them.
--
Ticket URL: <https://code.djangoproject.com/ticket/27211#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.89aebfbdcfeffe888443e26fca52550c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
