Correct HTTP cache request directives - #200
Draft
zaniebot wants to merge 1 commit into
Draft
Conversation
zaniebot
force-pushed
the
zb/bughunt200/163-fix-http-cache-request-directives
branch
from
July 16, 2026 02:34
56ea6c0 to
877d64b
Compare
astral-automations-bot
Bot
force-pushed
the
zb/bughunt200/163-fix-http-cache-request-directives
branch
from
July 17, 2026 21:43
877d64b to
70f610a
Compare
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.
Cached responses incorrectly become stale under
min-freshbecause the calculation uses epoch time;max-staleis read from the original request instead of the current one. Apply both directives to the cached response's age, as required by RFC 9111. This builds on the cache-age and exact-expiration fixes in uv#20178 and uv#20183.