Bug #73616 | mysqlbackup should handle 307 redirects for s3 | ||
---|---|---|---|
Submitted: | 17 Aug 2014 18:33 | Modified: | 9 Sep 2014 16:48 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Enterprise Backup | Severity: | S3 (Non-critical) |
Version: | 3.10.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | aws, Backup, cloud, s3 |
[17 Aug 2014 18:33]
Daniël van Eeden
[3 Sep 2014 12:56]
Sveta Smirnova
Thank you for the report. Is there any way to force AWS to do redirect or I simply should make enough tries until I hit the redirect?
[4 Sep 2014 7:43]
Daniël van Eeden
This is what I understand from the linked aws page: - If you create a new bucket in a non-US region (e.g. an europe region) and then imidiately try to use it you will get a redirect. This is because DNS hasn't yet propagated. - If you submit a request to the wrong endpoint then you will get a redirect. This is how I encountered it: - Created a new EU bucket - Tried to use it imidiately with mysqlbackup - Result: unhandled redirect This is how I think this could be tested: - Use /etc/hosts to redirect requests to the wrong endpoint - This should result in redirects.
[9 Sep 2014 16:48]
Sveta Smirnova
Thank you for the feedback. Verified as described. To repeat choose "Ireland" as region, then try to backup to it. Workaround: choose some US region.