From eccbd748d60a1ec6543c317c1073d9531e66d4a5 Mon Sep 17 00:00:00 2001 From: Adam Nelson Date: Thu, 13 Oct 2016 08:23:14 +1100 Subject: [PATCH] Gotcha for Cloudfront and host headers. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index cf09a61..2fb042a 100644 --- a/README.md +++ b/README.md @@ -1182,6 +1182,7 @@ CloudFront ### CloudFront Gotchas and Limitations - If using S3 as a backing store, remember that the endpoints for website hosting and for general S3 are different. Example: “bucketname.s3.amazonaws.com” is a standard S3 serving endpoint, but to have redirect and error page support, you need to use the website hosting endpoint listed for that bucket, e.g. “bucketname.s3-website-us-east-1.amazonaws.com” (or the appropriate region). +- 🔹By default, CloudFront will not forward HTTP Host: headers through to your origin servers. This can be problematic for your origin if you run multiple sites switched with host headers. You can [enable host header forwarding](http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorCustomOrigin.html#request-custom-headers-behavior) in the default cache behavior settings. DirectConnect -------------