#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 Jacob Walls <jacobtylerwalls@…>):
In [changeset:"b615947208ac89a30ef04e9827392958bb30c619" b615947]:
{{{#!CommitTicketReference repository=""
revision="b615947208ac89a30ef04e9827392958bb30c619"
[6.1.x] Refs #36560, CVE-2026-35193 -- Replaced substring check on cache-
control directives in UpdateCacheMiddleware.
Avoid false positives from hypothetical extension directives
that could be superstrings of the ones we are checking.
Backport of 142b881cecaddc334cabec139e701c0e4b9798da from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36560#comment:11>
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/0107019eace3a892-65da32cb-2fe6-4d1a-bace-dc8cbf587d5d-000000%40eu-central-1.amazonses.com.
