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
Hi,
I've been using golang with minio-go client (https://github.com/minio/minio-go) to Put and Get image objects to RiakCS, and it works splendidly.
But problem arised (I got Accessdenied error) when the object is accessed with url through browser hostname/bucketname/objectkey
*the object is put directly under the bucket
Hi, @kuenishi , maintainer from minio-go, @poornas , has been actively helping me to solve this issue.
it was pointed out to me that when minio-go client send API request to set a bucket policy :
---------START-HTTP---------
PUT /uploads/?policy= HTTP/1.1
Host: 192.168.34.170:8080
User-Agent: Minio (linux; amd64) minio-go/4.0.4
Content-Length: 417
Authorization: AWS **REDACTED**:**REDACTED**
Content-Md5: d4Sj0xE9GbH0UsQ4mjtPjQ==
Date: Thu, 07 Dec 2017 00:29:34 GMT
Accept-Encoding: gzip
HTTP/1.1 415 Unsupported Media Type
Content-Length: 0
Content-Type: application/json
Date: Thu, 07 Dec 2017 00:26:30 GMT
Server: Riak CS
---------END-HTTP---------
415 Unsupported Media Type
It is not sending content-type as a compliance with s3 spec . maybe Riak is expecting content-type header and throwing an error ?
Hi,
I've been using golang with minio-go client (https://github.com/minio/minio-go) to Put and Get image objects to RiakCS, and it works splendidly.
But problem arised (I got Accessdenied error) when the object is accessed with url through browser
hostname/bucketname/objectkey
*the object is put directly under the bucket
I've raised issue to minio-go (minio/minio-go#894) and it's pointed out to me that Riak CS needs to implement SetBucketPolicy API Handler. It's Probably because Bucket ACL's are deprecated and instead Bucket policies are implemented as in http://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-bucket-policy.html
I hope you can help me with this problem, Best Regards ~
The text was updated successfully, but these errors were encountered: