search

lavenderwords / s3-bash

Automatically exported from code.google.com/p/s3-bash
Other
0 stars 0 forks source link

XML Malformed #22

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. ./s3-put -T ./test2 -k <mykey> -v -s ./<mysecretkeyfile> 
/mybucketname

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

I expect to get a response containing the information that the upload has 
been completed. I get:

* About to connect() to s3.amazonaws.com port 80
*   Trying 72.21.211.225... connected
* Connected to s3.amazonaws.com (72.21.211.225) port 80
> PUT /com.pro2film.temp HTTP/1.1
> User-Agent: curl/7.15.5 (i486-pc-linux-gnu) libcurl/7.15.5 
OpenSSL/0.9.8c zlib/1.2.3 libidn/0.6.5
> Host: s3.amazonaws.com
> Accept: */*
> Date: Thu, 11 Feb 2010 11:29:33 +0000
> Authorization: AWS 
AKIAJACM2UHKEJLIJG7A:EtTlioSGV8wBDIM0gluQsjxrW/w=
> Content-Type: text/plain
> Content-MD5: EmqKUbnRu9B/3cZYGaVCww==
> Content-Length: 6
> Expect: 100-continue
> 
< HTTP/1.1 100 Continue
< HTTP/1.1 400 Bad Request
< x-amz-request-id: 3E3A50F42780BCA3
< x-amz-id-2: 
bbLKzrZgdElG/hZG93uakwo5sPCzGgs5APaHJeT7x5YziGaYpgXS1GQ9cj505
z75
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 11 Feb 2010 11:29:33 GMT
< nnCoection: close
< Server: AmazonS3
<?xml version="1.0" encoding="UTF-8"?>
* Connection #0 to host s3.amazonaws.com left intact
* Closing connection #0
<Error><Code>MalformedXML</Code><Message>The XML you provided 
was not well-formed or did not validate against our published 
schema</Message><RequestId>requestid</RequestId><HostId>hostid<
/HostId></Error>

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

Linux ec2-xx-xxx-xxx-xx.compute-1.amazonaws.com 2.6.16-xenU #1 
SMP Mon May 28 03:41:49 SAST 2007 i686 GNU/Linux

Please provide any additional information below.

Original issue reported on code.google.com by stefanoe...@gmail.com on 11 Feb 2010 at 11:31

GoogleCodeExporter commented 9 years ago 
solved: instead of 

./s3-put -T ./test2 -k <mykey> -v -s ./<mysecretkeyfile> 
/mybucketname

it must be:

./s3-put -T ./test2 -k <mykey> -v -s ./<mysecretkeyfile> 
/mybucketname/myfilename

Original comment by stefanoe...@gmail.com on 11 Feb 2010 at 1:01