feat: allow section-based Surrogate-Key to purge chunks#2851
Open
JacobCoffee wants to merge 6 commits intomainfrom
Open
feat: allow section-based Surrogate-Key to purge chunks#2851JacobCoffee wants to merge 6 commits intomainfrom
JacobCoffee wants to merge 6 commits intomainfrom
Conversation
…hings without nukiung the whole cache
JacobCoffee
commented
Dec 16, 2025
hugovk
approved these changes
Dec 16, 2025
JacobCoffee
commented
Dec 16, 2025
corneliusroemer
added a commit
to corneliusroemer/pythondotorg
that referenced
this pull request
Jan 4, 2026
… cause The “Please turn on JavaScript” notice can be shown even when JavaScript is enabled, e.g. due to intermittent asset loading or caching issues (python#2324, python#2851). This change updates the copy to explain why the notice is shown and to list possible causes without asserting that JavaScript is disabled on the client.
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.
Description
https://www.fastly.com/documentation/guides/full-site-delivery/purging/working-with-surrogate-keys/
When working with release changes lately we've needed to purge all releases because cache is wonky with stale CSS.
fastly ui and api doesnt seem to let me just do "root path, also purge all children" but maybe im missing it and we dont need this
Had to do something like this (which notably still missing pages like /downloads/android/ and others..):
Details
against
releases.txt:but ideally we just purge all of downloads/ when needed