I'm trying to serve content from s3 buckets that could be in any of the s3 regions.
I want fastly to follow the s3 url and cache the content.
This works fine for a 'standard' s3 url such as: mybucket.s3.amazonaws.com/path/to/content. I just set the host header to 'mybucket.s3.amazonaws.com' and set the backend to s3.amazonaws.com and it works great.
However if I have content stored in say a non-standard region, let's just say eu-central-1 e.g.:
http://myregionalbucket.s3.eu-central-1.amazonaws.com/path/to/content and I strip the region in the url to myregionalbucket.s3.amazonaws.com/... and set host header to myregionalbucket.s3.amazonaws.com, when I try with fastly I get a 307 Temp redirect back to the regional bucket url.
However using curl with the same url and host header, it works fine and I get a 200 with no redirects.
What is causing the request through fastly to trigger a 307 redirect.
Please sign in to leave a comment.