#27211: Include HTTP-caching headers to "304 Not Modified" responses
-------------------------------+------------------------------------
Reporter: renskiy | Owner: renskiy
Type: Bug | Status: assigned
Component: HTTP handling | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by timgraham):
* has_patch: 0 => 1
* type: New feature => Bug
* stage: Unreviewed => Accepted
Old 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]
New description:
According to [https://tools.ietf.org/html/rfc7232#section-4.1 RFC7232] all
"304 Not Modified" responses must include "Cache-Control" and "Expires"
headers that would have been sent in a corresponding "200 OK" response.
--
Comment:
[https://github.com/django/django/pull/7236 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/27211#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bea7be36df452a749355948236711c30%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
