-
-
Notifications
You must be signed in to change notification settings - Fork 752
ascanrulesBeta: Insecure HTTP Method rule - Address potential FP #6778
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
base: main
Are you sure you want to change the base?
Conversation
|
New Issues (12)Checkmarx found the following issues in this Pull Request
Fixed Issues (7)Great job! The following issues were fixed in this Pull Request
Use @Checkmarx to reach out to us for assistance. Just send a PR comment with Examples: |
464ca24 to
f85bce4
Compare
57bb411 to
1a3cc4e
Compare
|
It's unclear to me what's this is trying to achieve, address an FP or introduce more FPs? |
|
Hahaha okay. I'll revert the trim bit and just document it with a comment for future changes? |
|
Thank you for being specific, I'll review why I removed that. (It may have simply been a testing change that I forgot to revert before pushing.) |
1a3cc4e to
e609eb5
Compare
|
Addressed. |
2bdc234 to
482612a
Compare
|
Back to draft, just found another issue. |
Signed-off-by: kingthorin <[email protected]>
482612a to
8400f3f
Compare
|
It was a smaller issue than I initially thought, should be good to go now. |





Overview