Ari Chivukula
Ari Chivukula
I can see the utility, but it is a significant change in the meaning of the tag (allowing it to overwrite the Client Hints cache). That said, I can't imagine...
It's working for me in jsfiddle (which I believe executes the code in a third-party iframe) https://jsfiddle.net/653kgemv/ Are you getting any console messages and/or are you able to see the...
@abeyad @miketaylr
Chrome is actually limiting retries to once per origin per request. So if you have a chain like a.com -> b.com -> c.com your maximum retry chain length can look...
I'm writing a WPT for this case to verify
Haven't gotten to a working reproduction but will try again tomorrow here: https://chromium-review.googlesource.com/c/chromium/src/+/4377410
I was able to reproduce spec-respecting behavior (critical-ch being respected at the end (and/or in the middle) of a redirect chain as long as the chain is cross-origin) in https://chromium-review.googlesource.com/c/chromium/src/+/4377410...
@zhengweiwithoutthei could you take a look? It might be some sort of CORS issue.
Just to catch up on discussion, it sounds like the solution is a limit on the size of the Sec-CH-* headers in the HTTP request?
Notes from meeting with @annevk: * Issue is the *overall* size of headers sent via CORS * This is particularly an issue for Client Hints due to the large existing...