Skip to content

Add --stop-on-429 flag to stop scanning when the server rate limits - #663

Open
ChrisJr404 wants to merge 2 commits into
OJ:devfrom
ChrisJr404:stop-on-429
Open

Add --stop-on-429 flag to stop scanning when the server rate limits#663
ChrisJr404 wants to merge 2 commits into
OJ:devfrom
ChrisJr404:stop-on-429

Conversation

@ChrisJr404

Copy link
Copy Markdown

Fixes #363

Adds an opt-in --stop-on-429 flag. When it is set, gobuster stops the run as soon as one of the HTTP based modes (dir, vhost, fuzz) gets a 429 back, so you don't keep hammering a server that is already rate limiting you and risk getting the IP blocked.

It is off by default so nothing changes unless you ask for it, disabled by default and enabled by a cli flag like you suggested. The first worker to see a 429 prints a short message and cancels the run, the rest wind down cleanly and you get the normal Finished output.

Added tests for both the stop path and the default keep going path, and a small note in the readme. Based off the dev branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant