#30746: Add Feature-Policy header support
-----------------------------+-----------------------------------------
Reporter: Nick Pope | Owner: Nick Pope
Type: New feature | Status: assigned
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Someday/Maybe
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------+-----------------------------------------
Changes (by Nick Pope):
* needs_better_patch: 0 => 1
* has_patch: 0 => 1
* needs_docs: 0 => 1
Comment:
Replying to [comment:2 Adam (Chainz) Johnson]:
> I'm -1 on adding Feature-Policy to Django... right now. It's far too
experimental and evolving much faster than Django's release cycle.
>
> ...
>
> I think it'll be settled in a year or so and then it'll be worth adding
to Django core.
Replying to [comment:3 felixxm]:
> I agree with Adam, it's too early. This header is still under
development and it isn't wide-supported.
I understand and agree. I was hoping to look into supporting `Content-
Security-Policy` too for 3.1 and this is somewhat less complex, but also
similar in syntax, so exploring this will help. Thus I will probably
progress the [https://github.com/django/django/pull/11735 PR] as far as
possible for now and then leave it on ice. We'll have a better idea come
April~May 2020.
--
Ticket URL: <https://code.djangoproject.com/ticket/30746#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.8018fa4f8319ff3e22e7f37b6feaa050%40djangoproject.com.
