Feature detection and Accept: application/signed-exchanges headers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
For feature detection some of us have been discussing that we could add Accept: application/signed-exchanges headers. However given that SXG can have any resources it looks the UAs that support SXG always need to attach / append SXG type even when anything can be accepted, so it could look something like Accept: application/signed-exchange;q=0.9,*/*;q=0.8 for default, non-specific subresource requests. Would it be just or if we want to think about alternative feature detection mechanism (e.g. specific headers etc)?
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
No files, tests, or entry points are named. Start by reviewing the proposed Accept header and the alternative feature-detection mechanisms described in the issue; done means reaching a documented decision on the preferred approach.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100