Detect/report on redirect loops

[0xdevalias]

Currently, if a redirect loop is hit while using -r then gobuster spins a few times, then returns the following (at least if it's on the initial/base URL):

[-] Unable to connect: https://example.com/somepath/

gobuster/main.go

Line 412 in 7a6d1c0

fmt.Println("[-] Unable to connect:", s.Url)

Looking at my logs, the server is redirecting like so:

301 https://example.com/somepath/
301 https://example.com/somepath
301 https://example.com/somepath/
..etc..

Obviously, if we don't follow redirects with -r this issue won't happen.

This would be interesting to detect on, because in this instance, a non-existent folder will redirect to a 404, whereas an existing folder will enter this redirect loop.

[OJ]

ooh! Great catch! This could be the kind of thing that's causing other issues as well.