Repository navigation
fix(desktop): never cache responses whose CSP names the endpoints - #215
Merged
Merged
Conversation
Next serves static chunks as immutable, so Chromium kept the worker script, with the Content-Security-Policy for the endpoints configured when it was fetched. After switching endpoints the o1js worker could not reach the new node and proposals failed to read the vault state. The desktop server now sends no-store, and each launch clears the HTTP cache left by earlier releases.
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.
After changing endpoints, the desktop app's o1js worker could still be blocked from the new node: Chromium had cached the worker script (Next marks static chunks immutable) together with the Content-Security-Policy for the old endpoints. Proposals then failed with "Could not read the vault's on-chain state".
The desktop server now sends
Cache-Control: no-storeon everything it serves, and each launch clears the session's HTTP cache left by earlier releases. IndexedDB (compile cache, store checkpoints) is untouched.🤖 Generated with Claude Code