-
Notifications
You must be signed in to change notification settings - Fork 166
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
Observed words cause a 400 response. #75
Comments
same applies to semi colon |
any thoughts on this? |
Related to this. Certain characters are going to cause some servers to error e.g. 400 etc. I've noticed param miner doesn't treat 400 responses as a trigger to start narrowing the current header set to find the header causing the problem. Anyone know if its configurable anywhere to set certain server response codes to be 'interesting' ? |
@kinguardo you can kind of work around this by configuring the Reshaper plugin to remove characters in requests which you know are going to cause problems. Its a fiddle and requires trial and error is required but is a partial workaround. You can use the following as a template in Reshaper. You'll need to adjust the When's 'Matches Text' for a unique identifier in your applications URLs.
|
When running a scan with these 3 options enabled:
if an observed word contains a square bracket then it will be included in the header name. This causes the front-end to throw a
400
response very often because brackets aren't allowed in header namesThe text was updated successfully, but these errors were encountered: