Skip to content

fix: make sure connections freed on 304 (#60) - #62

Merged
paultiq merged 2 commits into
mainfrom
fix_60_304_close
Oct 11, 2026
Merged

paultiq merged 2 commits into
mainfrom
fix_60_304_close

Conversation

@paultiq

@paultiq paultiq commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Fixes: #60

@paultiq
paultiq merged commit eae6f44 into main Oct 11, 2026
10 checks passed
@paultiq
paultiq deleted the fix_60_304_close branch October 11, 2026 15:46

This branch was successfully deployed

1 active deployment
test — b87a0855 Deployed Oct 11, 2026 by paultiq via test (ubuntu-latest, 3.15t, httpx2) #190
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.

CachingTransport never closes the network response on a 304, so every revalidation holds a pooled connection until PoolTimeout

1 participant