I solved this for my use case, just recording it for posterity.
What steps will reproduce the problem?
> echo "LOL" | ./s3-bash.0.02/s3-put -v -k $AWS_ACCESS_KEY_ID -s ./s3.secret -T
- /$AWS_S3_BUCKET/lol
* Adding handle: conn: 0x7f9b24003a00
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7f9b24003a00) send_pipe: 1, recv_pipe: 0
* About to connect() to s3.amazonaws.com port 80 (#0)
* Trying 205.251.243.218...
* Connected to s3.amazonaws.com (205.251.243.218) port 80 (#0)
> PUT /$AWS_S3_BUCKET/crap HTTP/1.1
> User-Agent: curl/7.30.0
> Host: s3.amazonaws.com
> Accept: */*
> Transfer-Encoding: chunked
> Date: Wed, 19 Mar 2014 18:35:48 -0400
> Authorization: AWS $AWS_ACCESS_KEY_ID:lBA8y6rMz13fjMob4uXc+hzr+PE=
> Content-Type: text/plain
> Expect: 100-continue
>
< HTTP/1.1 501 Not Implemented
< x-amz-request-id: 5C28F3632FBB75CE
< x-amz-id-2: w+P5aTeoix/clMorAkWGftxvnn1HNLxBU/1uMVBfH62MirEtri8qhxovgP2Dm6RU
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Wed, 19 Mar 2014 22:35:48 GMT
< Connection: close
* Server AmazonS3 is not blacklisted
< Server: AmazonS3
<
<?xml version="1.0" encoding="UTF-8"?>
* Closing connection 0
<Error><Code>NotImplemented</Code><Message>A header you provided implies
functionality that is not
implemented</Message><Header>Transfer-Encoding</Header><RequestId>5C28F3632FBB75
CE</RequestId><HostId>w+P5aTeoix/clMorAkWGftxvnn1HNLxBU/1uMVBfH62MirEtri8qhxovgP
2Dm6RU</HostId></Error>
What is the expected output? What do you see instead?
It should have put the file in S3, or given an AccessDenied error.
What version of the product are you using? On what operating system?
v0.0.2, OS X Mavericks
Please provide any additional information below.
The solution for me was to not pass the data via STDIN but to instead pass a
filename.
Original issue reported on code.google.com by tsnowh...@taximagic.com on 19 Mar 2014 at 10:50
Original issue reported on code.google.com by
tsnowh...@taximagic.comon 19 Mar 2014 at 10:50