Change description:
Client hints allow browsers to provide origins with device-specific configuration data in the HTTP request headers. The client hints spec was recently updated to enable origins to request the browser to remember an origin-wide Accept-CH support for a specified period of time using Accept-CH-Lifetime header.
Changes to API surface:
- Support for Accept-CH-Lifetime response header would be added.
Links:
Public standards discussion:
https://github.com/httpwg/http-extensions/issues/306https://tools.ietf.org/html/draft-ietf-httpbis-client-hints-04#section-6.2
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.
We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.
For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit
For any questions, please contact owencm, sshruthi, larforge
There is still on TODO associated with this bug.
~~~[chrome/browser/client_hints/client_hints.cc]~~~
// TODO( crbug.com/735518 ): If the request is redirected, the client hint
// headers stay attached to the redirected request. Consider removing/adding
// the client hints headers if the request is redirected with a change in
// scheme or a change in the origin.
~~~
tbansal@, could you check if this TODO is fixed.
Note: I am adding support for removing headers here:
https://chromium-review.googlesource.com/c/chromium/src/+/1369856
It looks like this is what this comment was waiting for. Maybe.
Comment 1 by tbansal@chromium.org
, Jun 21 2017