-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
None-check when computing md5 #25655
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for picking this up! Change looks good to me. Just some comments on the CHANGELOG and test. Let me know if you have any questions.
API change check API changes are not detected in this pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks again!
[Hub Generated] Review request for Microsoft.Security to add version preview/2023-10-01-preview (Azure#25655) * Adds base for updating Microsoft.Security from version preview/2023-03-01-preview to version 2023-10-01-preview * Updates readme * Updates API version in new specs and examples * read.me fix * fix compiste version * add ciem configuration to new security connector * update ciem description * add ciem to custom words * add containers changes * add vm scanners to GCP DCSPM * add data sensitivity discovery * add containers to defender for containers * add containers to GCP containers and DCSPM * run prettier * fix readme file * remove old version from compsite package * add scan interval to examples
Description
Fix for #25489. Our md5 method was not considering the possibility that a request's content could be
None
instead ofb""
. Since from an HTTP perspectiveNone
andb""
are the same, we just add a simpleNone
-check,All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines