Fix Age header refresh on 304 revalidation#193
Merged
llfbandit merged 1 commit intollfbandit:masterfrom Mar 20, 2026
Merged
Conversation
Owner
|
Thanks for the contribution. |
petermnt
force-pushed
the
bugfix/304-cache-age
branch
from
21a5ce2 to
3fd93f9
Compare
Contributor
Author
Done |
llfbandit
added a commit
that referenced
this pull request
Mar 20, 2026
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
2 participants
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.
This updates 304 revalidation to refresh the cached Age header in both dio_cache_interceptor and http_cache_client.
Without this, revalidated entries could keep an outdated age baseline, which can skew freshness calculations in http_cache_core.