AWS SDK and multipart upload

Neil Soman <neil@xxxxxxxxxxxxxx> · Sat, 15 Mar 2014 14:17:24 -0700

Just FYI for any who might be using the AWS Java SDK with rgw.

There is a bug in older versions of the AWS SDK in the CompleteMultipartUpload call. The Etag that is sent in the manifest is not formatted correctly. This will cause rgw to return a 400.

e.g.
T 192.168.1.16:46532 -> 192.168.1.51:80 [AP]
POST /ed19074e-ed9a-488e-96e0-0d29b3704717/5bc1961c-215a-449e-9df4-c80b50ecfe64-multi-1394917767?uploadId=huS2ydwnDmOJ0vqu_CDCRJIIxvQuXfe HTTP/1.1.
Host: 192.168.1.51.
Authorization: AWS foo:bar.
Date: Sat, 15 Mar 2014 21:09:28 GMT.
User-Agent: aws-sdk-java/1.5.0 Linux/2.6.32-431.5.1.el6.x86_64 OpenJDK_64-Bit_Server_VM/24.45-b08/1.7.0_51.
Content-Type: text/plain.
Content-Length: 147.
Connection: Keep-Alive.
.
<CompleteMultipartUpload><Part><PartNumber>1</PartNumber><ETag>&quote;cd3573ccd5891f07fcd519881cc74738&quote;</ETag></Part></CompleteMultipartUpload>

The "&quote;" above should be "&quot;"

I moved to version 1.7.1 of the AWS SDK and multipart worked just fine.

If you already knew about it, please ignore :)
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com