-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Rename Feature-Policy header to Permissions-Policy #51
Comments
Hi @bepsvpt! Can you please update it soon? It shows a lot of errors on my website 😢 |
I did my own class that extends their class and rename it myself. The
errors are gone.
Also you can simply disable this section in config/secure-headers.php.
Still will appreciate it to be fixed in the package...
чт, 30 июл. 2020 г., 21:18 JUNO_OKYO <notifications@github.com>:
… Hi @bepsvpt <https://github.com/bepsvpt>! Can you please update it soon?
It shows a lot of errors on my website 😢
[image: image]
<https://user-images.githubusercontent.com/5250117/88958907-571e0280-d2cb-11ea-8ff4-e0c703ff8d91.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACLIQ7OG66AQCJ4NQ3RUO2LR6G2OHANCNFSM4PDOWESQ>
.
|
any updates on this one? |
6.2.0 adds https://github.com/bepsvpt/secure-headers/blob/6.2.0/config/secure-headers.php#L148-L159 |
worked like a charm. thanks 😄 |
The header gets changed correctly but the format of the values changed too.
|
Came across this as well after using https://observatory.mozilla.org/ . Hope to see it implemented and released. |
Note: |
According to the following link, the Feature-Policy header is now renamed to the Permissions-Policy.
https://www.w3.org/TR/permissions-policy-1/
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy
Since yesterday (July 20 2020) started to get errors in Console in the Chrome:
"Error with Feature-Policy header: Unrecognized feature: 'display-capture'."
The text was updated successfully, but these errors were encountered: