Skip to content
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] Filter by redirect destination or response header #1141

Open
sa7mon opened this issue May 10, 2024 · 3 comments
Open

[FEATURE REQUEST] Filter by redirect destination or response header #1141

sa7mon opened this issue May 10, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@sa7mon
Copy link

sa7mon commented May 10, 2024

Is your feature request related to a problem? Please describe.
When busting a certain URL, it will frequently redirect to a "maintenance" page. The Ferboxbuster output looks like this:

301      GET        0l        0w        0c https://example.com/WEB_2011 => https://example.com/pages/maintenance.html
301      GET        0l        0w        0c https://example.com/1024x768 => https://example.com/pages/maintenance.html
301      GET        0l        0w        0c https://example.com/1280x800 => https://example.com/pages/maintenance.html
301      GET        0l        0w        0c https://example.com/1440x900 => https://example.com/pages/maintenance.html

Describe the solution you'd like
An option to filter either by the 301 destination or by arbitrary response headers. I'd still like to see redirects to other pages in the output, but filter out redirects to specific pages.

Describe alternatives you've considered
I tried --filter-similar-to, but that compares the body of the filtered page with the body of the busted page which will not be similar since the busted page has no response body. Likewise, the --filter-regex flag also compares only the response body

@sa7mon sa7mon added the enhancement New feature or request label May 10, 2024
@epi052
Copy link
Owner

epi052 commented May 10, 2024

howdy, and thanks for submitting!

i agree that there's no built-in way to do what you're after. I don't like the idea of filtering by redirect location (pretty sure i turned down a similar proposal a while back).

On the other hand, filtering by headers, or modifying --filter-regex to include headers seem like reasonable changes that are generic enough to be useful to more than a single usecase.

@epi052
Copy link
Owner

epi052 commented May 12, 2024

there's a debug build here (untested), lmk how it does. you should be able to --filter-regex on headers

https://github.com/epi052/feroxbuster/actions/runs/9047212741

@sa7mon
Copy link
Author

sa7mon commented May 20, 2024

I'm a bit embarrassed to say, but I can't find the subdomain I was busting at the time when I created this issue so I'm not able to test it out but if the functionality works I'd say merge it!
Thank you for such a quick turnaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants