#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
-------------------------------------+-------------------------------------
Comment (by Natalia <124304+nessita@…>):
In [changeset:"366d9ae6e8d1469c04e9ebdc1bcd098fc14a3b1e" 366d9ae]:
{{{#!CommitTicketReference repository=""
revision="366d9ae6e8d1469c04e9ebdc1bcd098fc14a3b1e"
[5.2.x] Fixed CVE-2026-8404 -- Used Cache-Control directives case-
insensitively in UpdateCacheMiddleware.
Thanks Ahmed Badawe for the report, and Jacob Walls for reviews.
This commit includes:
[5.2.x] Fixed #36560 -- Prevented UpdateCacheMiddleware from caching
responses with Cache-Control 'no-cache' or 'no-store'.
Backport of ed7c1a56400d64f109f30df3ce697984cdad7c75 from main.
Backport of d618d7ae4fec727d5b582bd24f803c28d17bf7cd from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36560#comment:9>
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/0107019e8d97e1f6-5e4001a2-b000-48fa-87ec-46ced27fc9d8-000000%40eu-central-1.amazonses.com.
