Actions
Bug #18343
openError responses do not fully conform to AWS spec
Status:
Need More Info
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
While working with Jewel 10.2.2 I found that at least some error responses do not contain a Message section in the returned XML.
For reference here is the AWS spec:
http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html
For example, when requesting a bucket location for a bucket that does not exist the response is:
<Error><Code>NoSuchBucket</Code><BucketName>foo</BucketName><RequestId>tx00000000000000000be1f-00584b26f6-100d-default</RequestId><HostId>100d-default-default</HostId></Error>
Actions