fix: prevent browser caching of Klavis MCP servers list#347
Open
fix: prevent browser caching of Klavis MCP servers list#347
Conversation
Existing users weren't seeing new MCP servers after OTA updates because the /klavis/servers endpoint had no Cache-Control headers, allowing the browser to serve stale cached responses. - Add Cache-Control: no-store header to /klavis/servers endpoint - Add cache: 'no-store' to the frontend fetch request - Add revalidateOnFocus: true to SWR hook (matching useGetUserMCPIntegrations) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Greptile SummaryFixed browser caching issue preventing new Klavis MCP servers from appearing for existing users after OTA updates by adding
The changes implement defense-in-depth caching prevention at both layers (backend headers and frontend fetch options) to ensure users always receive the latest server list. Confidence Score: 5/5
Important Files Changed
Last reviewed commit: ce8cfa6 |
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
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
/klavis/serversendpoint had noCache-Controlheaders, allowing browsers to serve stale cached responsesChanges
Backend (1 file):
klavis.ts— AddedCache-Control: no-storeheader to/klavis/serversendpoint to prevent browser cachingFrontend (1 file):
useGetMCPServersList.tsx— Addedcache: 'no-store'to fetch request andrevalidateOnFocus: trueto SWR config (matching the pattern used byuseGetUserMCPIntegrations)Test plan
bun test— all 3 Klavis route tests pass🤖 Generated with Claude Code