#27211: Include HTTP-caching headers to "304 Not Modified" responses
-------------------------------+--------------------------------------
Reporter: renskiy | Owner: renskiy
Type: New feature | 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
-------------------------------+--------------------------------------
Description changed by renskiy:
Old description:
> Most browsers can cache responses with 304 HTTP code. So why not to
> include such headers to response if necessary.
New description:
Most browsers can cache responses with 304 HTTP code. So why not to
include such headers to response if necessary.
'''UPDATE''':
According to the [https://tools.ietf.org/html/rfc7232 RFC7232] all "304
Not Modified" responses must include "Cache-Control" and "Expires" headers
that would have been sent in a corresponding "200 OK" response.
See [https://tools.ietf.org/html/rfc7232#section-4.1 Section 4.1 of
RFC7232]
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27211#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.4ee3e023eed3c5ff5b8ca175525bf973%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
