Re: [whatwg/fetch] Why does Fetch specify a max redirect count of 20? (#576)

@ddragana It looks like for Chrome, there's generally more redirects these days. I have not done a deeper analysis as to when or why that transition may have occurred, such as internal redirects, mor HSTS, etc, but continuing to use the same methodology in https://github.com/whatwg/fetch/issues/576#issuecomment-342990393 (28DAU, Stable, all Chrome platforms), it looks like:

| Redirect Limit | Estimated # of Loads Broken, as percentage (0-100) |
| -- | -- |
| 16 | 0.00244% |
| 17 | 0.00231% |
| 18 | 0.00213% |
| 19 | 0.00177% |

You can work those numbers backwards - that is, 0.00177% of loads have 20 redirects. Setting the limit to 16 would break every load that used 17, 18, 19, or 20 redirects - hence the .00244% aggregate increase in URLs that would fail to load.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/576#issuecomment-586478760