Add CROSS_ORIGIN_EMBEDDER_POLICY and CROSS_ORIGIN_OPENER_POLICY constants
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 378
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 5
Description
I'm currently building a site using actix-web, which relies on the http crate for strongly-typed header constants, and I noticed that there are a couple of headers which don't yet have constants here, forcing me to resort to manually specifying them as strings.
Specifically:
As these headers need to be set to enable access to browser features like SharedArrayBuffer and un-throttled performance timers, I think it'd make sense to add CROSS_ORIGIN_EMBEDDER_POLICY and CROSS_ORIGIN_OPENER_POLICY constants.
Contributor guide
No contributing guide indexed for this repository
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
No source file or test is named in the issue. Locate the existing strongly typed HTTP header constants, add CROSS_ORIGIN_EMBEDDER_POLICY and CROSS_ORIGIN_OPENER_POLICY alongside them, and verify that the existing test suite accepts both constants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100