Project

General

Profile

Actions

Bug #24098

open

rgw: error codes mismatch on malformed acl PUT

Added by Dmitry Plyakin almost 6 years ago. Updated almost 6 years ago.

Status:
Triaged
Priority:
Normal
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

RGW returns "InvalidArgument" on PUT acl, when acl is malformed or empty.
Request:
PUT /bucket/?acl HTTP/1.1
Host: [rgw host]
Accept-Encoding: identity
Date: Fri, 11 May 2018 11:08:49 GMT
Content-Length: 31
Authorization: [authorization]
User-Agent: Boto/2.46.1 Python/2.7.12 Linux/4.4.0-121-generic

<AccessControlPolicy>

Response:
HTTP/1.1 400 Bad Request
...
<Error>
<Code>InvalidArgument</Code>
<BucketName>bucket</BucketName>
...
</Error>

AWS S3 returns "MalformedACLError" in this case.
Request:
PUT /?acl HTTP/1.1
Host: bucket.s3.amazonaws.com
Accept-Encoding: identity
Date: Fri, 11 May 2018 12:38:58 GMT
Content-Length: 31
Authorization: [authorization]
User-Agent: Boto/2.46.1 Python/2.7.12 Linux/4.4.0-121-generic

<AccessControlPolicy>

Response:
HTTP/1.1 400 Bad Request
...
<Error>
<Code>MalformedACLError</Code>
<Message>The XML you provided was not well-formed or did not validate against our published schema</Message>
...
</Error>

It seems to me that error code in RGW should be changed according to AWS.

Actions #1

Updated by Orit Wasserman almost 6 years ago

  • Status changed from New to Triaged
Actions #2

Updated by Orit Wasserman almost 6 years ago

  • Assignee set to Orit Wasserman
Actions

Also available in: Atom PDF