no support for South America (Sao Paulo) location

[GoogleCodeExporter]

s3fuse does not support buckets located in South America (Sao Paulo) location.

I can succesfully mount a bucket located in the Standard US location, but I 
have not tested other locations.

Mounting results in the following error, and directory is not available

$ s3fuse -f  -o  config=/home/tourigny/.s3fuse/s3fuse.conf -v -v -v 
/mnt/s3_tourigny/
openssl_locks::init: ssl version: OpenSSL/1.0.0e
request::run: request for [/tourigny/.Trash/] failed with code 301 and 
response: 
request::run: request for [/tourigny/.Trash] failed with code 301 and response: 

request::run: request for [/tourigny/.Trash-1000/] failed with code 301 and 
response: 
request::run: request for [/tourigny/.Trash-1000] failed with code 301 and 
response: 
readdir: path: /
request::run: request for [/tourigny] failed with code 301 and response: <?xml 
version="1.0" encoding="UTF-8"?>
<Error><Code>PermanentRedirect</Code><Message>The bucket you are attempting to 
access must be addressed using the specified endpoint. Please send all future 
requests to this 
endpoint.</Message><RequestId>DFAC28C9DC92CE6C</RequestId><Bucket>tourigny</Buck
et><HostId>FFqU9to1B3EcYCjXPru0iONzd9relIiUPGBA5tXgMLEXUNrqAFCplx9wIBXNWrSU</Hos
tId><Endpoint>tourigny.s3.amazonaws.com</Endpoint></Error>

Original issue reported on code.google.com by etiennet...@gmail.com on 6 Sep 2012 at 3:26

[GoogleCodeExporter]

If you don't mind fetching and building the code yourself, you can use the 
"aws_service_endpoint" configuration file option to set the endpoint to 
"s3-sa-east-1.amazonaws.com".  Otherwise, this new option will be in release 
0.12.

Original comment by tar...@bedeir.com on 15 Sep 2012 at 3:21

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by tar...@bedeir.com on 15 Sep 2012 at 8:35