-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
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
Define Critical-CH Restart logic more rigorously. #154
Comments
Should Critical-CH restarts be limited to idempotent requests (or even just GET)? |
Per https://github.com/WICG/client-hints-infrastructure/blob/main/reliability.md#retry-limits, it should be limited to just GET. I'm not sure what the Chromium implementation does tho. |
I guess we should verify there are tests to that effect.. |
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 like a.com -(retry)> a.com -> b.com -(retry)> a.com -> b.com -> c.com -(retry)> a.com -> b.com -> c.com. |
Also the current spec checks the Critical-CH on the result of creating navigation params by fetching, which is after all redirects. |
We need a formal way to indicate the entire navigation needs to be restarted from the top of the redirect chain.
The text was updated successfully, but these errors were encountered: