Timeline for Redirect homepage in S3 Routing Rules
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2024 at 3:05 | comment | added | phatmann | Object redirect on index.html does not work unless you actually type "index.html" into the URL. | |
| Aug 9, 2016 at 21:12 | comment | added | Michael - sqlbot |
Possible hackaround: add x-amz-website-redirect-location to the metadata of the object index.html (whatever you used as index document name) at the root of the bucket, with the value of https://new-site.example.com/product/. These are handled as 301, assuming S3 handles redirecting from an index document.
|
|
| Aug 9, 2016 at 21:06 | vote | accept | mlissner | ||
| Aug 9, 2016 at 21:06 | comment | added | mlissner | Shoot. This is where I annoyingly add more requirements that I forgot to mention. The other requirement is that I already have a catch-all rule, which redirects blog posts from the old domain to the new one. The blog posts simply map across so their old path is the same on the new domain. So, the root goes to the product page, feature pages (like the FAQ) get placed under the product page, and blog posts just map across (but can't be enumerated). I think the final solution is to just make the blog posts redirect to the product page. Lame, but it'll work. | |
| Aug 9, 2016 at 20:47 | history | answered | Michael - sqlbot | CC BY-SA 3.0 |