I'm having a problem uploading .json files when I set a Content-Type header.

s3cmd put --recursive --acl-public
--add-header="Content-Type":"application/json"
--add-header="Content-Encoding":"gzip" --exclude '*' --include '*.json'
"$DIR/" "$BUCKET"
--- Output ---
ERROR: S3 error: 403 (SignatureDoesNotMatch): The request signature we
calculated does not match the signature you provided. Check your key and
signing method.

The weird thing is, this works fine with .js files using:
s3cmd put --recursive --acl-public
--add-header="Content-Type":"application/javascript"
--add-header="Cache-Control":"public,max-age=30672000"
--add-header="Expires":"Sat, 21 Jan 2012 20:00:00 GMT"
--add-header="Content-Encoding":"gzip" --exclude '*' --include '*.js'
"$DIR/" "$BUCKET"

I can upload the .json files perfectly fine if I leave out the Content-Type
header. I tried using --guess-mime-type, but it just sets it to
binary/octet-stream. --guess-mime-types works fine with .js files.

Operating System: Ubuntu 10.10 (32-bit)
s3cmd Version: tested with both (sudo apt-get install s3cmd v1.0.0) and
(python setup.py install from source v1.0.0)

How do I fix this?
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
S3tools-general mailing list
S3tools-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/s3tools-general

Reply via email to