We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future versions of Chrome aim to block User Agent Strings and leverage Client Hints instead.
The "Device Hints" are especially important for OS metrics as well as our downloads page.
https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints https://developer.mozilla.org/en-US/docs/Glossary/Client_hints https://www.keycdn.com/blog/client-hints
The text was updated successfully, but these errors were encountered:
Initial draft of Sec-CH-UA* hints
4c34f5d
Per #552
Add Client Hints support (#643)
204e2cb
Add Sec-CH-UA* request headers in favor of legacy User-Agent string Closes #552
Update: Added new Bitness flags 1d8dda8.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Future versions of Chrome aim to block User Agent Strings and leverage Client Hints instead.
The "Device Hints" are especially important for OS metrics as well as our downloads page.
https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/client-hints
https://developer.mozilla.org/en-US/docs/Glossary/Client_hints
https://www.keycdn.com/blog/client-hints
The text was updated successfully, but these errors were encountered: