fix(api): harden cache-control headers for polymarket and rss-proxy#613
Merged
fix(api): harden cache-control headers for polymarket and rss-proxy#613
Conversation
- polymarket: use fixed s-maxage=120 instead of passing upstream cache-control (which could be no-cache) - rss-proxy: bump s-maxage from 600 to 900 to match max-age
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
s-maxage=120instead of forwarding upstream cache-control (which could beno-cache, defeating CDN caching)s-maxagefrom 600→900 to matchmax-age, with 300s stale-while-revalidateTest plan
s-maxage=120headers-maxage=900header