#36560: When the Cache-Control header is set to no-store, the response is
cached.
-------------------------------------+-------------------------------------
Reporter: mengxun | Owner: mengxun
Type: | Status: closed
Cleanup/optimization |
Component: HTTP handling | Version: 5.2
Severity: Normal | Resolution: fixed
Keywords: cache | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"ed7c1a56400d64f109f30df3ce697984cdad7c75" ed7c1a56]:
{{{#!CommitTicketReference repository=""
revision="ed7c1a56400d64f109f30df3ce697984cdad7c75"
Fixed #36560 -- Prevented UpdateCacheMiddleware from caching responses
with Cache-Control 'no-cache' or 'no-store'.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36560#comment:8>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198cd1a7875-bdf23e79-9827-4a0c-9ce0-bb6be9a061bd-000000%40eu-central-1.amazonses.com.
