-
Notifications
You must be signed in to change notification settings - Fork 22.9k
permissions-policy is not forbidden request or response header #41938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Preview URLs Flaws (3)URL:
(comment last updated: 2025-11-14 06:04:49) |
|
This is not a single instance. The problem is that before #38296, a nontrivial number of pages wrote "Forbidden header name" as if it meant "forbidden request or response header name", but in fact the spec uses this term explicitly for "Forbidden request header name", so when #38296 updated all pages to use the unambiguous new term, these pages become blatantly wrong (whereas they were covertly wrong before). For example, |
|
Oh, I searched for |
|
@Josh-Cena Yes. Thanks for the clarification. We should fix this everywhere.
There is no easy way to automate this. The starting sentence for every header is supposed to say this, but I doubt does so reliably (i.e. So it has to be manual. I personally am happy for this to be the start of that work. |
|
You can do a search for
|
This comment was marked as spam.
This comment was marked as spam.
|
OK, I've done all of the other listed response headers in #41946 - we might still be missing some of course. |
files/en-us/web/http/reference/headers/permissions-policy/index.md
Outdated
Show resolved
Hide resolved
bsmth
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments in the linked PR, but leaving a +1 here, too 👍🏻
Fixes #41843
Permissions-Policy is not a forbidden request header.