#15727: Add support for Content-Security-Policy (CSP) to core
-------------------------------------+-------------------------------------
Reporter: db.pub.mail@… | Owner: Rob
| Hudson
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
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
-------------------------------------+-------------------------------------
Comment (by nessita <124304+nessita@…>):
In [changeset:"ff0ff98d427982b7225df59f454a86bdf66251d6" ff0ff98]:
{{{#!CommitTicketReference repository=""
revision="ff0ff98d427982b7225df59f454a86bdf66251d6"
Refs #15727 -- Updated AdminSeleniumTestCase to use
ContentSecurityPolicyMiddleware.
Replaced the custom CSP middleware previously used in the admin's
AdminSeleniumTestCase with the official ContentSecurityPolicyMiddleware.
This change ensures alignment with Django's built-in CSP support.
Also updates the test logic to inspect browser console logs to assert
that no CSP violations are triggered during Selenium admin tests.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15727#comment:52>
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/01070197b2c02483-fe5f7e87-288e-4f87-bf2d-c632288120e1-000000%40eu-central-1.amazonses.com.