-
-
Notifications
You must be signed in to change notification settings - Fork 456
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
[FEATURE REQUEST] Is there an option to not go for another request before the tool didn't receive a response from the server #1136
Comments
howdy! you should be able to use https://epi052.github.io/feroxbuster-docs/docs/configuration/limit-connections/ |
i tried that but it didnt work still i see multiple requests going without waiting the response from the server, here is the url example: https://www.poledesanteduvilleneuvois.fr/ |
i also added : --rate-limit 1 but still without success |
|
well i guess we get banned in the few requests at the beginning so you think u can improve the tool behavior ? |
ultimately, what you want is a synchronous client, and feroxbuster doesn't support that. if you happen to write rust code, i have a library you could use to build your own synchronous fuzzer https://github.com/epi052/feroxfuzz |
Oh i see thanks for your response im not good on rust. Do you know any other tool that works synchronously ? |
you can check gobuster/ffuf/wfuzz. there are others, but some names are escaping me rn. gobuster and ffuf are both async tools, so may have a similar problem to ferox in that regard. wfuzz may be single threaded but im not sure. if you truly need something super slow, you could always wirte a simple python script with requests
|
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when the server ban my ip since its very slow to respond to a request, takes about 15 seconds to respond to a request
Describe the solution you'd like
an option to not go for another request before the tool didn't receive a response from the server
The text was updated successfully, but these errors were encountered: