Report requests: use Sec-CH-UA?
Open
@clelland is already working on this.
Since Aug 15, 2022.
- Dominant language
- Bikeshed
- Stars
- 84
- Forks
- 39
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
As of today, requests sent by the browser to the defined endpoint(s) also include a user-agent field, as described here.
Each report has a user agent, which is the value of the User-Agent header of the request from which the report was generated.
With user-agent string reduction in mind, what are the plans for the user agent info in report requests?
Will the approach here change as well?
- If not: Why not?
- If yes: Would it make sense to start making available in the requests sent by the browser new fields that match
Sec-CH-UA?
Example values:
Sec-CH-UA: "Chromium";v="93", "Google Chrome";v="93", " Not;A Brand";v="99"
Sec-CH-UA-Mobile: ?0-
Sec-CH-UA-Platform: "macOS"
By default, Chrome already returns all of these in regular requests.
Benefits of this could be twofold:
- Help existing report collectors get ready for upcoming changes in Chrome and other browsers.
- Make it easier for report collectors and custom endpoints to parse and the UA information, and make it useful.
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.
Assessment
This issue has not been assessed yet.