Closed n0kovo closed 4 months ago
yea, looking through the code, it makes sense that this would hang things (though that's not intended/desirable, lol).
the robots request happens very early in the scan. when this errors out, it exits the scan event handler, making it so that no other directories can be queued/processed.
really appreciate the repro code! ill lyk when it's fixed
give the build here a try and lmk how it goes
https://github.com/epi052/feroxbuster/actions/runs/8019002224
@all-contributors add @n0kovo for bug
@epi052
I've put up a pull request to add @n0kovo! :tada:
merged into main, dropping new release soon
The logic flow somewhere along these lines, leads to what I assume is an infinite loop, if a redirection loop occurs at
/robots.txt
, and stalls Feroxbuster competely. I wanted to do a PR, but it turns out I'm not a Rust programmer.Version: 2.10.1
Steps to reproduce:
Server on
http://127.0.0.1:5000
:Trace output:
Thanks for an awesome tool!