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

Looking at a 28DA of Chrome 62 users 

| Total Redirect Count | Individual Percentage | User Breakage Percentage |
|------------------|-------------|---------|
| 0 | 97.95675 | - |
| 1 | 01.62609 | 2.04310 |
| 2 | 00.28255 | 0.41622 |
| 3 | 00.10431 | 0.13367 |
| 4 | 00.01719 | 0.02935 |
| 5 | 00.00582 | 0.02159 |
| 6 | 00.00284 | 0.00634 |
| 7 | 00.00086 | 0.00350 |
| 8 | 00.00076 | 0.00264 |
| 9 | 00.00043 | 0.00188 |
| 10 | 00.00044 | 0.00145 |
| 11 | 00.00018 | 0.00101 |
| 12 | 00.00019 | 0.00083 |
| 13 | 00.00014 | 0.00064 |
| 14 | 00.00012 | 0.00050 |
| 15 | 00.00017 | 0.00038 |
| 16 | 00.00008 | 0.00021 |
| 17 | 00.00009 | 0.00013 |
| 18 | 00.00003 | 0.00004 |
| 19 | 00.00002 | 0.00002 |

These counts are Beta, and do include internal redirects. I should have better numbers in ~10 weeks (once 62 is released to stable and has time to widely distribute and bake)

Based on [Blink principles of web compatibility](https://docs.google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit#heading=h.83o2xr8ayal6), dropping the max below 11 is probably at the "larger compatibility threshold" (it's > 'small-but-non-trivial'). Dropping to 6 would break ~ 0.006% of Chrome loads.

-- 
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-335919258