New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect/report on redirect loops #64
Labels
Comments
ooh! Great catch! This could be the kind of thing that's causing other issues as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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):gobuster/main.go
Line 412 in 7a6d1c0
Looking at my logs, the server is redirecting like so:
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.
The text was updated successfully, but these errors were encountered: