#31923: Add Support for Cross-Origin Embedder Policy and Cross-Origin Resource
Policy Headers
-------------------------------------+-------------------------------------
Reporter: meggles711 | Owner:
| meggles711
Type: New feature | Status: assigned
Component: HTTP handling | Version: dev
Severity: Normal | Resolution:
Keywords: COEP, header, CORP, | Triage Stage:
security | Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Florian Apolloner):
Yeah I think you could add those know. An probably also COOP (Cross-
Origin-Opener-Policy) and the acronyms are getting ridiculously
confusing. Okay, the written header names as well but that is another
story :D
As for the settings explosion, we should really start thinking about
those. The security middleware will have quite a few after a while :d
--
Ticket URL: <https://code.djangoproject.com/ticket/31923#comment:5>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/068.e4fdd39f26a823001dee52d755cd7e1d%40djangoproject.com.
