Bug #15231
closedradosgw returning 400 bad URI
0%
Description
Attempting to connect to the radosgw through the aws-sdk-go, I receive a Error 400: Bad request while attempting to list buckets.
The header sent by the client (DE-Master is the gateway node)
GET http://DE-Master:7480/ HTTP/1.1
Host: DE-Master:7480
User-Agent: aws-sdk-go/1.1.12 (go1.6; linux; amd64)
Authorization: AWS4-HMAC-SHA256 Credential={{ObscuredACCESSKEY}}/20160322/default/s3/aws4_request, SignedHeaders=host;x-amz-date, Signature=cc05e75b7ae742bbad73704fd978f59d61f32d0863a5dea9ebc65165de6d7278
X-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
X-Amz-Date: 20160322T000052Z
Accept-Encoding: gzip
I receive the response:
HTTP/1.1 400 Bad Request
Content-Length: 60
Connection: keep-alive
Date: Tue, 22 Mar 2016 00:00:50 GMT
Error 400: Bad Request
Invalid URI: [http://DE-Master:7480/]
I suspect this is because rgw does not support absolute paths.
Updated by Jonathan Fraser about 8 years ago
Sorry just caught this is a duplicate of #12917, please ignore
Updated by Nathan Cutler about 8 years ago
- Related to Bug #12917: RGW does not support absolute URI added
Updated by Nathan Cutler about 8 years ago
- Related to deleted (Bug #12917: RGW does not support absolute URI)
Updated by Nathan Cutler about 8 years ago
- Is duplicate of Bug #12917: RGW does not support absolute URI added