-
-
Notifications
You must be signed in to change notification settings - Fork 255
Add unexpected_responses.js script #240
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
Conversation
This comment has been minimized.
This comment has been minimized.
This is another variation on the "do something if we see a surprising response" theme, but is intended to be more flexible: * Response codes are tested against a regular expression rather than a literal value * A sense code is used to indicate if matching the regex is "good" or "bad", so you can either whitelist or blacklist depending on your particular use case * Failures (unexpected responses) generate alerts. The formatting here was tailored for mechanical consumption, but there are suggestions in the comments if you value "pretty" output Signed-off-by: Scott Bailey <scott.bailey@godaddy.com>
c11b8b4 to
2f4565c
Compare
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Scott Bailey <scott.bailey@godaddy.com>
|
Could you update https://github.com/zaproxy/community-scripts/blob/main/CHANGELOG.md with an added note in the unreleased section? Also you seem to have committed with two different accounts, if that's something that matters to you, feel free to tweak it and force push. |
Signed-off-by: Scott Bailey <scott.bailey@godaddy.com>
Done.
I don't care that much -- they're both me. ;-) |
Signed-off-by: Scott Bailey <scott.bailey@godaddy.com>
|
Thank you! |
This is another variation on the "do something if we see a surprising response" theme, but is intended to be more flexible: