Actions
Bug #59433
opens3 error response missing Message field
% Done:
0%
Source:
Tags:
s3 low-hanging-fruit backport_processed
Backport:
pacific quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
Description
some clients like veeam fail to decode the xml Error response if it's missing the Message field
Updated by David Orman about 1 year ago
Casey Bodley wrote:
some clients like veeam fail to decode the xml Error response if it's missing the Message field
More detail, example requests from Amazon S3:
b'\n<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>test</Key><RequestId>XXXXXXXXX</RequestId><HostId>XXXXXXXXXXXX</HostId></Error>'
b'\n<Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist</Message><BucketName>ldkjfkldjflk</BucketName><RequestId>XXXXXXXXXXXXXXXXXXXXXX</RequestId><HostId>XXXXXXXXXXXXXXX</HostId></Error>'
Updated by Casey Bodley about 1 year ago
- Status changed from New to Fix Under Review
- Pull request ID set to 51052
Updated by Cory Snyder about 1 year ago
- Related to Backport #59528: pacific: s3 error response missing Message field added
Updated by Casey Bodley 12 months ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot 12 months ago
- Copied to Backport #59613: pacific: s3 error response missing Message field added
Updated by Backport Bot 12 months ago
- Copied to Backport #59614: reef: s3 error response missing Message field added
Updated by Backport Bot 12 months ago
- Copied to Backport #59615: quincy: s3 error response missing Message field added
Updated by Backport Bot 12 months ago
- Tags changed from s3 low-hanging-fruit to s3 low-hanging-fruit backport_processed
Actions