exclude specific paths during recursive scans

It's already possible with --exclude-subdirs

exclude specific paths during recursive scans

It's already possible with --exclude-subdirs

i'm not that mean, what i mean is in some cases, during scanning, especially recursive scanning, it may trigger WAF or redirection, resulting in a large number of consecutive HTTP response status codes of 200 with the same size. In such cases, it should be skipped directly."

@AMG4MATIC Understood. When performing scanning activities, such as recursive scanning, it is possible that it may trigger a Web Application Firewall (WAF) or redirection, resulting in a large number of consecutive HTTP response status codes of 200 with the same size. In these cases, it may be advisable to skip these responses directly in order to avoid unnecessary scanning and potential detection by security mechanisms. Skipping these responses can help avoid false positives or unnecessary noise in the scanning process. However, it's important to always ensure that any scanning activities are performed in a responsible and legal manner, with proper authorization and adherence to applicable laws and regulations.

Its just like a:
wfuzz -c -z stdin http://site.com/FUZZ --filter 'w|u()'
And only old wfuzz can do this.

Its just like a: wfuzz -c -z stdin http://site.com/FUZZ --filter 'w|u()' And only old wfuzz can do this.

--filter 'w|u()' seems to get all results and then filter only unique responses, but it requires the scanning to totally finish before showing the results right?