This repository was archived by the owner on Oct 21, 2025. It is now read-only.
Reduce the HttpClient timeout to the fastest latency found so far#8
Merged
manuelmayer-dev merged 2 commits intomanuelmayer-dev:mainfrom Apr 3, 2025
FrankRay78:Reduce-the-HttpClient-timeout-to-the-fastest-latency-found-so-far
Merged
Reduce the HttpClient timeout to the fastest latency found so far#8manuelmayer-dev merged 2 commits intomanuelmayer-dev:mainfrom FrankRay78:Reduce-the-HttpClient-timeout-to-the-fastest-latency-found-so-far
manuelmayer-dev merged 2 commits intomanuelmayer-dev:mainfrom
FrankRay78:Reduce-the-HttpClient-timeout-to-the-fastest-latency-found-so-far
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When testing the latency of each speedtest server, sometimes a server will timeout after a long while (aka throws a socket exception).
This change avoids unnecessary waiting by successively reducing the HttpClient timeout to the fastest server/latency found so far.
(ie. do not wait for servers where the response time becomes longer than the fastest).