-
-
Notifications
You must be signed in to change notification settings - Fork 405
feat: add variable to skip response rules #3944
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
feat: add variable to skip response rules #3944
Conversation
6e714ca
to
06bcc6a
Compare
Good thinking. I like the approach and I think this is useful. But it is a lot of skip rules. What about skipping to the beginning of 959 in a single skip? (Or the end of 959.) |
Definitely a better approach to just skip to the end instead. |
fee9051
to
8ac9913
Compare
@M4tteoP For the quantitative tests to work (and post the comment) we should use the |
8ac9913
to
a4b3bbc
Compare
Signed-off-by: Felipe Zipitria <felipe.zipitria@owasp.org>
Co-authored-by: Max Leske <250711+theseion@users.noreply.github.com>
Signed-off-by: Felipe Zipitria <felipe.zipitria@owasp.org>
Signed-off-by: Felipe Zipitria <felipe.zipitria@owasp.org>
a4b3bbc
to
456a8c3
Compare
📊 Quantitative test results for language: |
Looks like working now! 🥳 |
@dune73 Any other comments? Shall we merge? |
This looks good. So fair with me to merge. One word of caution, you may still want to consider. The variable is called I have been thinking about situations where you would want to skip the former but not the latter. So far I can't see such a situation, but conceptually, there is a chance such a situation exists and you might prefer to skip to the beginning of 959. |
Sure. I don't see how variables might be incremented in the case of CRS, but other rules might come into play so we can add it back. |
Add jump in a4b139c. |
Very good. Thank you. |
what
SecResponseBodyAccess
beingOn
by default.why
references
todo