I read `doFollowingRedirects` with an elided comma - that is, 'do, following redirects (as you go)'. In that context, the function doesn't seem so surprising.

I read `doFollowingRedirects` with an elided comma - that is, 'do, following redirects (as you go)'. In that context, the function doesn't seem so surprising. If you take a look at the function `Do`[0], you'll notice it calls out to either 'send' or 'doFollowingRedirects' depending on whether it's a request that should 'do, following redirects' or simply 'send a single request'. Many HTTP libraries I've seen are structured around creating a request object and then handing it to a 'do request' function - the crime here at best seems to be the naming 'doFollowingRedirects', which can be read as 'do the subsequent redirects' which might make it seem odd that the first request was included in the for loop therein.