Skip to content

[BUG] Ferox buster doesn't recognise 301 with protocol change #815

@sectroyer

Description

@sectroyer

Describe the bug
If application makes a 301 redirection and switches protocols feroxbuster doesn't recognise the redirection.

To Reproduce
Scan an application that behaves like the one below:
200 GET 459l 1201w 16218c https://example.com/
301 GET 7l 20w 237c https://example.com/css => http://example.com/css/
301 GET 7l 20w 236c https://example.com/js => http://example.com/js/

Just to make things clear after redirecting to http://example.com/js/ app redirects browser back to https://example.com/js/.
I have encountered multiple applications with this behaviour

Expected behavior
Feroxbuster either should have a flag to ignore protocol change or in case of protocol change follow redirection to make sure it doesn't point to same application.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions