naototty / s3backer

Automatically exported from code.google.com/p/s3backer
GNU General Public License v2.0
0 stars 0 forks source link

s3backer fails on buckets outside the "US Standard" region #33

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Make an S3 bucket in region "Ireland".
2. Apply s3backer to it.

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

s3backer fails to read or write to the bucket with messages like

* Failed writing received data to disk/application

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

s3backer-1.3.2 on Mac OS X 10.7

rb@Crane$ uname -a
Darwin Crane.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 
2011; root:xnu-1504.15.3~1/RELEASE_I386 i386

Please provide any additional information below.

Reading the source code I found the debug-http flag and used it.  Amazon is 
sending back HTTP 301 "Moved Permanently" responses to requests.

< HTTP/1.1 301 Moved Permanently
...
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Date: Thu, 04 Aug 2011 15:28:54 GMT
< Connection: close
< Server: AmazonS3

These do not seem to include a changed location header.

I'm happy to report that s3backer seems to be working fine for me with a bucket 
in the US Standard region.

Original issue reported on code.google.com by richard....@gmail.com on 4 Aug 2011 at 3:46

GoogleCodeExporter commented 8 years ago
I've just found the --vhost option, which fixes this.  Apologies.

(As a suggestion, the docs could use the word "region", since Amazon uses that. 
I would've found it sooner. Thanks!)

Original comment by richard....@gmail.com on 4 Aug 2011 at 5:26

GoogleCodeExporter commented 8 years ago
No problem, sorry for the confusion. I've added a note to the man page.

Original comment by archie.c...@gmail.com on 4 Aug 2011 at 8:35