Avoid year-long caching of missing asset responses - #24
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
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.
Production verification confirmed missing assets now return 404, but nginx still attached a one-year immutable cache header to that error response. Remove
alwaysfrom the asset cache directive so successful responses retain long-lived caching and 4xx/5xx responses do not.The production nginx change is limited to monitor.moss.land. Validated the nginx configuration before and after the change and reloaded successfully. Production checks confirm the real JavaScript asset returns 200 with immutable caching; a missing asset returns 404 without Cache-Control.