Repository navigation
Conversation
A download or upload URL that answered with an error status was timed as if it carried data and requested again without a pause, and a download whose requests all failed was reported as 0 Mbps. Such a server now fails like one that is down.
A server could answer with a redirect to an http:// URL, and the probe, the IP lookup, the transfers and the telemetry request followed it. A run that asked for HTTPS was then measured, or its result sent, over plain HTTP.
BKPepe
force-pushed
the
fix/transfer-status-codes
branch
from
November 22, 2026 14:34
c34f6d4 to
45a48a8
Compare
This branch has not been deployed
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.
Two commits. The second needs the first.
A download or upload URL that answers with an error status was timed as if the error pages were data, and requested again without a pause. Such an answer no longer counts, and neither does a 307 or 308 to an upload, which the client does not follow. Each stream waits 200 ms before it asks again, and a server with no successful request fails like one that is down.
Under
--securea server could redirect tohttp://, and the probe, the IP lookup, the transfers and the telemetry request followed. Such a redirect is now refused.Download URL answering 404, 5 s, local server:
Upload requests that fail in transport are left as they are, because
--timeoutcovers the whole request body. This overlaps #154 inUpload.