Reports compression
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 84
- Forks
- 39
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
AFAICT, right now there's no way to define a compression scheme that will be applied to the reports. There is no HTTP mechanism for requests to perform content negotiation on the uploaded content.
It's probably better to define a compression scheme as part of the spec, have the server declare its preference for compression as part of the Report-To header, and have the browser apply that compression before sending the reports up.
/cc @mikewest
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 by reading the Reporting API specification and the issue's discussion of content negotiation, the Report-To header, and browser-side compression. Done would require an agreed compression scheme and a complete specification of how the server declares it and how reports are compressed before upload.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100