Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PutObject throws error from AWS SDK #633

Closed
drgomesp opened this issue Mar 30, 2017 · 11 comments
Closed

PutObject throws error from AWS SDK #633

drgomesp opened this issue Mar 30, 2017 · 11 comments

Comments

@drgomesp
Copy link

When trying to PutObject, I'm getting the following message from AWS SDK:

A header you provided implies functionality that is not implemented

Possibly related to aws/aws-sdk-go#122

Any ideas?

@balamurugana
Copy link
Member

@drgomesp

  • If you are using minio server and awk-sdk-go, please provide minio version, setup type you use and awk-sdk-go version.

  • If you are using minio-go with amazon s3, please use TraceOn() and provide the output.

@balamurugana
Copy link
Member

@drgomesp for minio-go tracing, refer http://docs.minio.io/docs/golang-client-api-reference#TraceOn

@drgomesp
Copy link
Author

drgomesp commented Mar 30, 2017

This is what I'm getting:

---------START-HTTP---------
PUT /mongodb/00010110.json HTTP/1.1
Host: pf-mongodb-backup.s3-ap-southeast-1.amazonaws.com
User-Agent: Minio (darwin; amd64) minio-go/2.0.3
Content-Length: 0
Authorization: #####
Content-Md5: 1B2M2Y8AsgTpgAmY7PhCfg==
Content-Type: application/octet-stream
Expect: 100-continue
X-Amz-Content-Sha256: UNSIGNED-PAYLOAD
X-Amz-Date: 20170330T094611Z
Accept-Encoding: gzip

HTTP/1.1 501 Not Implemented
Connection: close
Transfer-Encoding: chunked
Content-Type: application/xml
Date: Thu, 30 Mar 2017 09:46:11 GMT
Server: AmazonS3
X-Amz-Id-2: Tt7eks5WnICUgCHv96Gc5vNtoxjjhNwjnIEq2U5umrLKnXOlFhXGmB9cGWI2u1QA+AnNwwywkCA=
X-Amz-Request-Id: A568F217B5E2F1A2
---------END-HTTP---------

@vadmeste
Copy link
Member

@drgomesp, looks like the bug is fixed in the last master, can you test with it ?

@harshavardhana
Copy link
Member

Expect: 100-continue

HTTP/1.1 501 Not Implemented

This is because of the Expect header new S3 endpoints don't yet support this.

@harshavardhana
Copy link
Member

@drgomesp can you apply this PR locally and test out for us? #640

Thanks.

@harshavardhana harshavardhana self-assigned this Apr 4, 2017
@drgomesp
Copy link
Author

drgomesp commented Apr 5, 2017

Apparently the issue happened because the file was empty. It was a problem on my application level, but the error message was not very helpful.

Can we try adding a more helpful feedback?

@harshavardhana
Copy link
Member

We cannot server sent the error. We can't know what to say at this point in time. Because the error sent by server is arbitrary. So as a client we can't make sense of anything that went wrong.

@vadmeste
Copy link
Member

vadmeste commented Apr 5, 2017

@drgomesp, were you able to test with minio-go master ?

@deekoder
Copy link
Contributor

@drgomesp I will go ahead and close this issue. Please do reopen if you think we have not addressed this correctly.

@drgomesp
Copy link
Author

@deekoder no problem. As I said before, I think we need a proper message when throwing this error. Otherwise, it works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants