You must provide the Content-Length HTTP header

[GoogleCodeExporter]

What steps will reproduce the problem?
1. s3-put -k KEYHERE -s /backup/.s3-priv -T /backup/2008-05-27-db.sql.gz -c
application/x-gzip /backup/2008-05-27-db.sql.gz

What is the expected output? What do you see instead?

I expected to be able to upload this file (11GB), but instead I received:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>MissingContentLength</Code><Message>You must provide the
Content-Length HTTP
header.</Message><RequestId>00B7B167008F078D</RequestId><HostId>n2Kb1dVEDdNsqRO4
wgL9R5x04mb3/+QN6iUdTkCbVZDmImdcFjpwuuqiSnv1ANIq</HostId></Error>

What version of the product are you using? On what operating system?

S3-bash 0.02

Please provide any additional information below.

curl 7.16.3 (amd64-portbld-freebsd7.0) libcurl/7.16.3 OpenSSL/0.9.8e
zlib/1.2.3 libssh2/0.18
Protocols: tftp ftp telnet dict ldap http file https ftps scp sftp 
Features: IPv6 Largefile NTLM SSL libz 

Original issue reported on code.google.com by klimp...@gmail.com on 28 May 2008 at 5:34

[GoogleCodeExporter]

OK, sorry for the noise. The error was a 41 byte long secrets file.

Is there a way to catch those (didn't see anything), and also, any plans for
.s3bashrc? :)

Original comment by klimp...@gmail.com on 28 May 2008 at 5:55

[GoogleCodeExporter]

How did you diagnose and fix this issue?

Original comment by philwin...@gmail.com on 28 Aug 2008 at 3:25

[GoogleCodeExporter]

I think I provided the "clue"? =) I just made sure the secrets file is 40 byte, 
I
think a simple "ls -l /path/to/your/secrets/file" will do the trick and show 
you if
the file is of correct size.

Original comment by klimp...@gmail.com on 28 Aug 2008 at 10:26

[GoogleCodeExporter]

My 40 character secret key is always saving as a 41 byte file. I'm getting this 
same
problem.

Original comment by fitzt...@gmail.com on 22 Oct 2008 at 3:13

[GoogleCodeExporter]

Strike that. The discussion from Issue #1 helped me solve it. Props to azulgan's
comment #15 making it easy.

Original comment by fitzt...@gmail.com on 22 Oct 2008 at 3:32

[GoogleCodeExporter]

Easily fixed by using something other than VIM or Notepad. Try using nano - 
that's
how I fixed mine. The problem is that a lot of text editors append a line return
character at the end.

Original comment by philwin...@gmail.com on 22 Oct 2008 at 3:32

[GoogleCodeExporter]

Try this to fix your secret key file:

echo -n "yourSecretKey" > secret_key_file

Original comment by dtompk...@gmail.com on 25 Nov 2008 at 11:42