-
Notifications
You must be signed in to change notification settings - Fork 41
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: Inject Headers #3
Comments
Thanks for the suggestion @movsxd. I've considered this a bunch so far, and will think about how/if we can do this. Basically, the tool was built specifically for query string injections, and while it could migrate more broadly, I'm not sure if that's the best direction to take as there are other tools out there focused on more broad scanning. Either way, appreciate it and I'll think a bit about this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It may be useful to be able to inject headers on a rule basis in addition to specifying them on the command line. This would allow us to test rules like the following using the already built-in functionality for response matching:
This could also be extended to further tests such as X-Host, X-Forwarded-Host, X-Forwarded-Server being reflected in the response, or Host header SSRF's.
The benefit to having this feature as a rule instead of setting a blanket header for every request is that some hosts and endpoints may respond badly to them.
The text was updated successfully, but these errors were encountered: