Limitations of the --no-recursion Flag

[YxY2032]

When I enable the --no-recursion flag, if my wordlist contains directories like admin/login, it still performs recursive scanning — for example, it will continue scanning paths under /admin/login/. I strongly request the author to add a new option that completely disables recursive scanning under all circumstances.

[epi052]

howdy! I'm not able to reproduce the behavior you're describing. I setup a small test bed described below.

The sample directory structure

$ tree no-recursion-test/
no-recursion-test/
└── CVS
    ├── Entries
    │   └── index.html
    └── Root

my wordlist contains

CVS/Entries
CVS/Repository
CVS/Root

command used

feroxbuster -u http://localhost:8001 --no-recursion --scan-dir-listings

results

404      GET       13l       32w      335c Auto-filtering found 404-like response and created new filter; toggle off with --dont-filter
200      GET       15l       25w      220c http://localhost:8001/
301      GET        0l        0w        0c http://localhost:8001/CVS => http://localhost:8001/CVS/
200      GET        1l        1w        6c http://localhost:8001/CVS/Root
[####################] - 7s         2/2       0s      found:3       errors:0      
[####################] - 6s      4736/4736    772/s   http://localhost:8001/  

If you have an environment I can test against where the behavior described is exhibited, that would be helpful.