Fix stale HTML + prevent indexing of backups#26
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2f53392159
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Cache-Control: public, max-age=0, must-revalidate | ||
|
|
||
| /assets/* | ||
| Cache-Control: public, max-age=31536000, immutable |
There was a problem hiding this comment.
Avoid combining contradictory Cache-Control rules
This global Cache-Control rule also matches /assets/*, and on Cloudflare Pages multiple matching _headers rules are merged with duplicate header values comma-joined, so assets will receive both max-age=0, must-revalidate and max-age=31536000, immutable in the same header value. That makes asset caching behavior ambiguous and can defeat the intended long-lived asset cache policy.
Useful? React with 👍 / 👎.
This directly addresses stale pages showing in Google and improves crawl accuracy.