You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During developing Riak S2 client library, I've found inconsistency of current API implementation and documentation (v2.1.1).
GET Bucket success response has wrong order of elements in its body. According to Amazon S3 schema definition, Owner follows StorageClass element in the ListEntry type (example from Riak S2 documentation has different order).
GET Bucket query string parameters should be written in lower case and with dashes as words separators, according to Amazon S3 documentation, and it currently works this way. Looks like misspelling in Riak S2 documentation which describes them in camel case: Delimiter, Marker, `MaxKeys
PUT Bucket Policy request should return 204 No Content status code on success (now it's 200 OK, No body).
List Multipart Uploads response types ListMultipartUploadsResult.Upload.Key and ListMultipartUploadsResult.Upload.UploadId are actually strings (Riak S2 and Amazon S3 documentations descibe these parameters as integers).
The text was updated successfully, but these errors were encountered:
Basho-JIRA
changed the title
Inconsistency of API implementation and documentation
Inconsistency of API implementation and documentation [JIRA: RCS-377]
Nov 4, 2016
During developing Riak S2 client library, I've found inconsistency of current API implementation and documentation (v2.1.1).
GET Bucket
success response has wrong order of elements in its body. According to Amazon S3 schema definition,Owner
followsStorageClass
element in theListEntry
type (example from Riak S2 documentation has different order).http://docs.basho.com/riak/cs/2.1.1/references/apis/storage/s3/get-bucket
http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGET.html
GET Bucket
query string parameters should be written in lower case and with dashes as words separators, according to Amazon S3 documentation, and it currently works this way. Looks like misspelling in Riak S2 documentation which describes them in camel case:Delimiter
,Marker
, `MaxKeysPUT Bucket Policy
request should return204 No Content
status code on success (now it's200 OK
, No body).http://docs.basho.com/riak/cs/2.1.1/references/apis/storage/s3/put-bucket-policy
http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTpolicy.html
DELETE Bucket Policy
request should return204 No Content
status code on success (now it's200 OK
, No body)http://docs.basho.com/riak/cs/2.1.1/references/apis/storage/s3/delete-bucket-policy
http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketDELETEpolicy.html
List Multipart Uploads
response typesListMultipartUploadsResult.Upload.Key
andListMultipartUploadsResult.Upload.UploadId
are actually strings (Riak S2 and Amazon S3 documentations descibe these parameters as integers).http://docs.basho.com/riak/cs/2.1.1/references/apis/storage/s3/list-multipart-uploads
http://docs.aws.amazon.com/AmazonS3/latest/API/mpUploadListMPUpload.html
The text was updated successfully, but these errors were encountered: