#28833: "Cache-Control: private" responses should not be cached by server
-------------------------------------+-------------------------------------
Reporter: Nathan Vander Wilt | Owner:
Type: | shangdahao
Cleanup/optimization | Status: closed
Component: HTTP handling | Version: 1.8
Severity: Normal | Resolution: fixed
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 Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"d968788b57f41b7def88046d1178fd2932a32a4e" d968788b]:
{{{
#!CommitTicketReference repository=""
revision="d968788b57f41b7def88046d1178fd2932a32a4e"
Fixed #28833 -- Prevented CacheMiddleware from caching responses with
"Cache-Control: private".
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28833#comment:6>
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/064.f5086befe6178613b34e2f8f61f5f005%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.