Updates xml error unmarshalling to look at all request id keys when p… #2764
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.
…opulating error information
Motivation and Context
When XML type error responses are received and the chain
AwsS3ProtocolFactory -> AwsXmlErrorTransformer -> AwsXmlErrorUnmarshaller
is activated, responses with empty body only populate therequestId
value in the exception if the header contains the keyx-amzn-RequestId
and not the alternatex-amz-request-id
Description
Attempts to find any valid request id key in the response headers
Testing
Validated using the S3 head object API call
Types of changes
Checklist
mvn install
succeedsLicense