Why is my CloudFront distribution serving stale HTML files despite me invalidating the root path in the AWS console?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Why is my CloudFront distribution serving stale HTML files despite me invalidating the root path in the AWS console?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
AWS CloudFront invalidation path root slash does not invalidate index.html cache behavior cache key official documentation Google ↗
AWS CloudFront troubleshoot stale content browser cache origin cache-control headers service worker official docs Google ↗
- What you need to know when invalidating paths · docs.aws.amazon.com
- Amazon CloudFront · docs.aws.amazon.com
- How CloudFront processes HTTP 4xx and 5xx status codes from your origin · docs.aws.amazon.com
- Troubleshoot "X-Cache: Miss from CloudFront" response · repost.aws
- Manage how long content stays in the cache (expiration) · docs.aws.amazon.com
- Host Single Page Applications (SPA) with Tiered TTLs on CloudFront and S3 · aws.amazon.com
- invalidation guide · docs.aws.amazon.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
AWS CloudFront invalidation path root slash does not invalidate index.html cache behavior cache key official documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
AWS CloudFront troubleshoot stale content browser cache origin cache-control headers service worker official docs OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |