#31840: Adding Support for Cross-Origin Opener Policy
-------------------------------------+-------------------------------------
Reporter: meggles711 | Owner:
| meggles711
Type: New feature | Status: assigned
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: COOP, security, | Triage Stage: Accepted
headers |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by meggles711):
Okay, sounds good, I'll cc some other developers and have them review my
code before I make a pull request. I'll also check out the thread you
started on the mailing list.
I was considering pitching adding support for COOP and another header
called Cross-Origin Embedder Policy (COEP) in the same issue. However,
COEP relies on having a specific CORS or CORP header setting which Django
doesn't currently have support for right now either. Maybe I consider
tackling COEP and CORS/CORP now as well so that they don't have to be
raised as 2 additional issues that are just adding security headers?
--
Ticket URL: <https://code.djangoproject.com/ticket/31840#comment:4>
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.f905702abea8f8c73ac4233ac78f665a%40djangoproject.com.
