Repository navigation
fastcgi: add max_conns_per_host - #8426
Open
joshbarros wants to merge 3 commits into
Open
joshbarros wants to merge 3 commits into
joshbarros wants to merge 3 commits into
Conversation
FastCGI opens a connection per request. Add max_conns_per_host to cap concurrent connections per upstream address, releasing the slot when the response body is closed. Zero keeps the current unlimited behavior.
|
✅ Contributor License Agreement All identified contributors have signed the CLA. Thank you! |
joshbarros
force-pushed
the
feat/7082-fastcgi-max-conns
branch
from
November 17, 2026 14:22
043e2f3 to
23459a4
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
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.
Fixes #7082
The FastCGI transport opens a connection per request and had no way to cap concurrency, unlike the HTTP transport's
max_conns_per_host.Add
max_conns_per_hostto the transport. A per-address semaphore blocks a request until a slot is free or the request context is cancelled, and the slot is released when the response body closes. Zero keeps the current unlimited behavior. Tests cover blocking, a different upstream, and release.