[Cyberduck-trac] [Cyberduck] #10790: Support me-south-1 region

Cyberduck trac at cyberduck.io
Fri May 1 19:03:32 UTC 2020

#10790: Support me-south-1 region
 Reporter:  seme1                  |         Owner:  dkocher
     Type:  feature                |        Status:  reopened
 Priority:  normal                 |     Milestone:  8.0
Component:  s3                     |       Version:  7.0.1
 Severity:  normal                 |    Resolution:
 Keywords:  s3 Bahrain me-south-1  |  Architecture:
 Platform:  Windows 10             |

Comment (by dkocher):

 > The legacy global endpoint is also used for virtual hosted-style
 requests in other supported Regions. If you create a bucket in a Region
 that was launched before March 20, 2019 and use the legacy global
 endpoint, Amazon S3 updates the DNS to reroute the request to the correct
 location, which might take time. In the meantime, the default rule
 applies, and your virtual hosted–style request goes to the US East (N.
 Virginia) Region. Amazon S3 then redirects it with an HTTP 307 redirect to
 the correct Region. For S3 buckets in Regions launched after March 20,
 2019, the DNS doesn't route your request directly to the AWS Region where
 your bucket resides. It returns an HTTP 400 Bad Request error instead. For
 more information, see Request redirection and the REST API.

Ticket URL: <https://trac.cyberduck.io/ticket/10790#comment:5>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows

More information about the Cyberduck-trac mailing list