phanes.vrm ?v=1 cache-bust#107
Merged
Merged
Conversation
phanes.vrm was added without a ?v=N query, so Cloudflare cached the deploy-window 404 with a 7-day TTL and served it to real users (the VRM loader would 404 -> Phanes never renders). Per the kill-the-build asset-cache rule every avatar asset must carry a ?v=N (chibis use ?v=2, etc.). Loader now fetches /avatars/phanes.vrm?v=1 (+ preview ?v=1), a fresh URL CF hasn't cached. File on disk is unchanged (the static server ignores the query). Co-Authored-By: Claude Opus 4.8 <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.
Adds ?v=1 to the phanes.vrm asset URL so the VRM loader bypasses the Cloudflare-cached 404 (file already on prod; URL-only change).