#27211: Include HTTP-caching headers to "304 Not Modified" responses
-------------------------------------+-------------------------------------
Reporter: renskiy | Owner: renskiy
Type: Bug | Status: closed
Component: HTTP handling | Version: 1.10
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f9702977b72003c17db87d6e4fdaa36415f13a38" f9702977]:
{{{
#!CommitTicketReference repository=""
revision="f9702977b72003c17db87d6e4fdaa36415f13a38"
Fixed #27211 -- Made UpdateCacheMiddleware include caching headers for
"304 Not Modified" responses.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27211#comment:7>
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.4993079a0d188d9c6adb04f7476599c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
