Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024-11-22 weekly sync #479

Merged

Conversation

gumpt
Copy link
Contributor

@gumpt gumpt commented Nov 22, 2024

No description provided.

drcaramelsyrup and others added 6 commits November 22, 2024 14:50
The h2 crate does not appear to check for content-length underflow if
only a header frame is received with END_STREAM.
After a request is predicted uncacheable and bypasses cache, it may
still be cached if the response is a 200. However, HEAD responses are
not normally cacheable as they don't include the actual response body.
The PUT request body itself may be chunked, but normally clients send
the body that ought to be cached without chunked encoding applied.
Includes-commit: d26d344
Replicated-from: #471
Co-authored-by: Matthew Gumport <[email protected]>
The cache locks may be held after serving stale, proxy upstream filter,
or revalidate uncacheable resulting in dangling cache locks.
Also only disable cache on final error if cache was not already
disabled, and add DeclinedToUpstream / UpstreamError no cache reasons.
@gumpt gumpt force-pushed the bleeper-mgumport-89319e9383d6f99066dfeace750a553d45e1c167 branch from 9fafee8 to 725329f Compare November 22, 2024 22:52
@drcaramelsyrup drcaramelsyrup merged commit e309436 into main Nov 23, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants