`Feature-Policy` should be called `Permissions-Policy` now, having a bit different syntax
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Is your feature request related to a problem? Please describe.
Permissions Policy, W3C Working Draft, 16 July 2020 specifies that Feature-Policy is now called Permissions Policy.
If Nextcloud implements these headers they should be kept up to date.
Describe the solution you'd like
At
Permissions-Policy should be generated instead of Feature-Policy.
Permissions-Policy has slightly different syntax.
Describe alternatives you've considered
Both Permissions-Policy and Feature-Policy are generated.
Additional context
securityheaders.com post on the topic - Goodbye Feature Policy and hello Permissions Policy!
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in lib/public/AppFramework/Http/Response.php around line 243 and compare the generated header with the linked Permissions Policy specification. Update the header name and syntax as described, then verify that the response emits the current Permissions-Policy form rather than Feature-Policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100