#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
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* cc: Adam (Chainz) Johnson, Nick Pope (added)
* stage: Unreviewed => Accepted
Comment:
OK, thanks. I'll provisionally Accept this, but cc a couple of people
who've been involved before here, and also
[https://groups.google.com/d/topic/django-
developers/WJAbbwJKp30/discussion I've raised a question on the mailing
list], since I'm not sure about ''just keep adding settings'' as the best
approach here. (Maybe we adjust the "Accept" to something else...?)
#30746 is the same ballpark here for Permissions-Policy
--
Ticket URL: <https://code.djangoproject.com/ticket/31840#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.e7449ae4f9ad21bfbec0378e44ec8ed3%40djangoproject.com.
