Description
Following feedback from a customer struggling with moving from AWS S3 to Riak CS.
Customer Issue 1: Today we compared the output of the s3cmd and our code and we discovered that with RIAK it’s virtually mandatory to specify the content-type of the
file at the time of starting the multipart request: if you do not do that
then the file will not have a content-type when stored on RIAK.
Action 1a: The overview page (http://docs.basho.com/riakcs/latest/cookbooks/Multipart-Upload-Overview/#Multipart-Upload-Phases) has information on the inclusion of metadata. This could be a good place to add guidance on specifying a content-type.
Action 1b: Update the example pages (http://docs.basho.com/riakcs/latest/references/apis/storage/s3/RiakCS-Initiate-Multipart-Upload/) to include specifying a content-type.
Customer Issue 2: It should be noted that, in this situation, RIAK will end up with a server side 500 error when trying to download the file without specifying in the request
header “Accept: /” (and most of the browsers will not do that).
Action 2: As there is no support for the request-content-type header, this could be documented at http://docs.basho.com/riakcs/latest/references/apis/storage/s3/RiakCS-GET-Object/
Customer Issue 3: During our analysis we also discovered that RIAK appears to not support the standard S3 override parameter mechanism, as we tried to override the
content type from the server using response-content-type: we did not spend
a lot of time on this one, but if this is the case then we suggest you to
update the documentation.
Action 3: Expand comparison matrix (http://docs.basho.com/riakcs/latest/references/apis/storage/s3/#API-Feature-Comparison) to include headers. S3 information available at http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadInitiate.html
http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html
http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectGET.html