forked from erpc/erpc
-
Notifications
You must be signed in to change notification settings - Fork 1
PLA-507: Make HTTP client timeouts configurable #5
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
Closed
0x666c6f
wants to merge
5
commits into
main
from
feature/pla-507-make-http-client-timeouts-configurable
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
19bec07
fix: avoid panicking and fail-open when rate limiter redis is not ava…
aramalipoor 3593281
feat: make HTTP client timeouts configurable
0x666c6f a522736
feat: add upstream defaults inheritance for HTTP client timeouts
0x666c6f 1c92c08
fix: add validation and logging for HTTP client timeouts
0x666c6f cca84aa
fix: add expectContinueTimeout validation and improve proxy pool erro…
0x666c6f File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The relationship checks only run when
timeoutis explicitly set, so configs likeresponseHeaderTimeout: 120s(ortlsHandshakeTimeout: 120s) withtimeoutomitted pass validation, butResolve()later appliesDefaultHTTPClientTimeout(60s). That means the request still times out at 60s even though the header/handshake timeout appears longer, which defeats the intent and yields surprising early timeouts. Consider validating these fields against the default timeout whentimeoutis zero, or adjusting resolution to enforceTimeout >= ResponseHeaderTimeout/TLSHandshakeTimeoutafter defaults are applied.Useful? React with 👍 / 👎.