Repository navigation
[Website] Replace the generic proxy with a cached Blueprints index - #4471
Merged
Merged
Conversation
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.
Replaces
/proxy/network-first-fetch/<url>with/blueprints-index.json. The service worker fetches only the Blueprints directory index from GitHub, parses it, and returns a new JSON response withnosniff. Upstream HTML and headers are never served as a Playground document.Keeps the last valid index for offline use. The directory UI uses the new endpoint. Removed proxy routes return 404 before the asset cache is consulted.
No domain or embedding-policy changes.
Testing
/blueprints-index.json, go offline, and load it again. The cached JSON should still load./proxy/network-first-fetch/…URL. It should return 404.