Project

General

Profile

Actions
Copy link

Bug #18343

open

Error responses do not fully conform to AWS spec

Added by Tim Jenkins over 7 years ago. Updated about 7 years ago.

Status:
Need More Info
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
Ceph - v10.2.2
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
Copy link
 #1

Updated by Chang Liu over 7 years ago

Hi, Time, I'm working on it. https://github.com/ceph/ceph/pull/12485

Actions
Copy link
 #2

Updated by Matt Benjamin about 7 years ago

  • Status changed from New to Need More Info

Hi, is this proposal still active? The PR above was closed-by-author.

Actions
Copy link
 #3

Updated by Dave Holland about 7 years ago

I would like to see this included too, can I help?

Actions
Copy link

Also available in: Atom PDF