Description

When you try to put an object into a bucket located in EU, you get an error from amazon, that this bucket must be accessed using the specific endpoint (bucketname.s3.amazonaws.com).
I have changed the function _makeRequest as follows. It seems to work so far with these changes. Haven't tested intensively.

IMHO it would be a good idea to handle Amazon S3 API permanent redirects, which seem to use the HTTP status 301 and do not set a location header (and are therefore not handled by Zend_HTTP_Client).

Posted by Jon Whitcraft (sidhighwind) on 2009-05-19T12:35:15.000+0000

Kristof,

I didn't write this component to i'm not too entierly sure what you are talking about. Can you please provide the docs page that explains that or submit a patch?

Posted by Kristof Coomans (cyberwolf) on 2009-05-19T12:45:26.000+0000

Hi Jon

You can find more information about it at http://docs.amazonwebservices.com/AmazonS3/latest/…, under "Permanent Request Redirection". After thinking a bit more about this, it might be better to use domain-style requests after all, as Ivo suggests. That works in all cases (EU and US-located buckets).

Posted by Jon Whitcraft (sidhighwind) on 2009-05-20T08:43:42.000+0000

This has been resolved and checked-in to svn.

Posted by Peter Ritter (pinopinelli) on 2009-06-29T06:10:29.000+0000

Hello,

are you shure that is suitable for all operations that can be done?
When I try to DELETE an object from a bucket (in the EU) then I get an positive response from S3. But my object is still there.
I guess the problem is, that Amazon's API also returns this positive response when you try to delete an object that does not even exist.
I did not test for other operations yet.