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

@wanderview @annevk Now that Chrome 62 has been on Stable for ~3 weeks, I went back and revisited these numbers over a 28DA for our stable users (e.g. including 'early' stable). Looking at just the buckets under discussion, I end up with

| Redirect Limit | Estimated Breakage percentage |
|---------------|------------|
| 16 | 0.00037 |
| 17 | 0.00024 |
| 18 | 0.00009 |
| 19 | 0.00004 |

So the numbers do show that, when factoring in a more broad set of users, there is a greater chance of breakage, but these numbers seem within the thresholds that Chromium has generally been happy with for deprecations.

Notably, this is still not distinguishing internal vs network redirects (which is not easily accomplished with our current architecture).

I'm curious if Chrome were to look at aligning with Safari, what the sense is from Firefox about similarly aligning, so 16 redirects. I'm also curious for folks sentiments regarding the internal v network - I don't actually think that's a thing that necessarily needs alignment, since we're talking about things such as, say, extensions, which already carve holes into the assurances of the platform (e.g. CSP)

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