Revalidate examples on every load instead of trusting the ten-minute page cache - #5
Merged
Merged
Conversation
…t hidden by the ten-minute page cache Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
GitHub Pages serves
examples/*withcache-control: max-age=600, andapp.jsfetched them with the default cache mode, so a visitor who opened an example within ten minutes before a deploy kept the old copy without any request being made — seen today right after #4 landed (the old truchet, with its E041, was still loaded from the browser cache while the server already returned the fixed file).fetch(..., { cache: 'no-cache' })on the manifest and the example files revalidates against the ETag on every load; when nothing changed the server answers 304 and no body is transferred.