You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually lot of subdomains have rate limits while bruteforcing for directories gobuster should stop if server responds with 429 status code but gobuster does not stop or exit and runs until wordlist which is meaning less and sometimes depending on implementation server might blacklist IP address
Solution
This should be implemented directly however if not at least a --stop-at-rtl flag should be available
I would love to contribute if agreed
The text was updated successfully, but these errors were encountered:
I also encountered this issue, however rather than stopping I think a throttling mechanism would be more useful.
If you are going to fix this you should consider:
throttling after 429 (your case)
throttling by default, it would be useful if something more advanced of a rate limit is in place;
edge cases such as X-RateLimit-Limit header (common in APIs)
Description
Usually lot of subdomains have rate limits while bruteforcing for directories gobuster should stop if server responds with 429 status code but gobuster does not stop or exit and runs until wordlist which is meaning less and sometimes depending on implementation server might blacklist IP address
Solution
This should be implemented directly however if not at least a
--stop-at-rtl
flag should be availableI would love to contribute if agreed
The text was updated successfully, but these errors were encountered: