-
Notifications
You must be signed in to change notification settings - Fork 571
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
chore(middleware-flexible-checksums): use RequestChecksumCalculation and ResponseChecksumValidation #6492
base: main
Are you sure you want to change the base?
Conversation
This reverts commit ba24558. The ResponseChecksumValidation should be consumed in request middleware.
…equestValidationModeMember]
The PR is ready for review. It's marked as draft, as it shouldn't be merged at this time. |
const responseChecksumValidation = await config.responseChecksumValidation(); | ||
|
||
if (requestValidationModeMember && responseChecksumValidation === ResponseChecksumValidation.WHEN_SUPPORTED) { | ||
input[requestValidationModeMember] = "ENABLED"; |
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.
what happens if the if
conditions are true but input[requestValidationModeMember]
is set by the user to some other value than ENABLED
(ignoring the fact that this is the only enum value)?
I would expect us to allow the value through and allow the user to receive a validation exception from the server.
Issue
flexibleChecksumsInterceptorMiddleware
Description
flexibleChecksumsInterceptorMiddleware
to populateinput[requestValidationModeMember]
Testing
Unit testing in CI
Also, verified that checksums are computed by default
Output
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.