Added option to toggle automatic following redirects

[ruyadorno]

Hi @floatdrop and @sindresorhus,

I'm opening this PR with the goal of illustrating what such an option as described on #165 would look like.

Please review at your own discretion.

Thanks in advance 👍

[knksmith57]

+1

[sindresorhus]

After much thinking I'm 👍 on this. @floatdrop You ok with this?

[floatdrop]

@sindresorhus how about merge this with maxRedirects option? For example -1 in maxRedirects will disable redirect following.

[sindresorhus]

@floatdrop We don't have a maxRedirects option. ?

[floatdrop]

@sindresorhus yep, just an idea.

[sindresorhus]

I'm not a big fan of -1 input, and in that case it could just be 0, but still, I don't really see the need for a maxRedirects option, and since we have neither at the moment, I'd rather just expose a followRedirects option that is actually requested by multiple people.

[ruyadorno]

rebased

[RoobinGood]

@ruyadorno are you sure that making redirect a successful result for request is a good idea? As far as I know it is not usual behavior.

[ruyadorno]

@RoobinGood that's a good point, I'm not really sure of anything 😊

It does make sense in the context of the original use case behind this idea, as described in #165 but at the end of the day I just want to access the original redirect HTTP response in case of a 300 error, I guess that could also be achieved by attaching the response to the thrown got.HTTPError object but then I'm even less sure that's a better option.

It's also worth noting that we're talking about an optional configuration, it won't change the way got behaves if you don't use the followRedirect config property.

[floatdrop]

@sindresorhus @ruyadorno are we ready to merge this option?

[ruyadorno]

👍 sure, it was a good point brought to the discussion by @RoobinGood but I still think the current implementation is better 😊 we're getting more people interested in having this option... let's merge this