fix: case-sensitive header lookup in HttpResponse getValue method #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, the
getValue
method in HttpResponse performs a case-sensitive lookup of header keys after lowercasing the input key. This causes issues when response headers like "Digest" need to be retrieved as part of verification.While creating the transient token, response from
/flex/v2/tokens
request contains a response header ofDigest
. CallingDigestHelper.verifyResponseDigest()
will always throw amissingDigestHeader
error when attempting to assigndigestHeader
value:This change modifies the
HttpResponse.getValue()
function to: