mirror of
https://github.com/nickpoida/og-aws.git
synced 2025-02-13 18:32:01 +00:00
Gotcha for Cloudfront and host headers.
This commit is contained in:
parent
c2c1bde233
commit
eccbd748d6
1 changed files with 1 additions and 0 deletions
|
@ -1182,6 +1182,7 @@ CloudFront
|
||||||
### CloudFront Gotchas and Limitations
|
### 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).
|
- 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
|
DirectConnect
|
||||||
-------------
|
-------------
|
||||||
|
|
Loading…
Reference in a new issue