- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
The legacy cache settings that you've provided effectively disable caching, and forward everything to the Origin. You can replicate this using cache policies and origin request policies, by using managed policies as follows:
Cache policy: CachingDisabled
Origin request policy: AllViewer
Caching in CloudFront is highly configurable, and it's very unusual that someone would need to disable caching in all cases - you will certainly need to do this for dynamic content, but you should try to maximize it for any static content that you have. I recommend that you read the documentation on optimizing caching and availability to try to maximize your use of the cache: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/ConfiguringCaching.html
Allowing your content to be served from the cache will reduce the number of requests being made to your origin, and reduce response times and latency for your viewers.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor 8 Monaten