-
Notifications
You must be signed in to change notification settings - Fork 234
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: algesten/ureq
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3.4.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: algesten/ureq
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.4.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 13 files changed
- 4 contributors
Commits on Aug 23, 2026
-
Buffer read_json into memory when Content-Length is below the limit (#…
…1191) * Buffer read_json into memory when Content-Length is below the limit serde_json's from_reader parses the response one byte at a time, which is noticeably slower than parsing an in-memory slice. When the Content-Length signals the body comfortably fits within the read limit, buffer it into a Vec and parse with from_slice instead. A 1/3-of-limit cutoff keeps the buffered bytes plus the deserialized value within the configured memory budget, and chunked or oversized responses fall back to the existing streaming path. Closes #1151 Co-authored-by: Chris (ChrisJr404) <11917633+ChrisJr404@users.noreply.github.com> Co-authored-by: Martin Algesten <martin@algesten.se>
Configuration menu - View commit details
-
Copy full SHA for 662410b - Browse repository at this point
Copy the full SHA 662410bView commit details -
Complete TLS handshakes while connecting (#1193)
* Complete TLS handshakes while connecting Both TLS backends defer the handshake until the request is written, after the connection phase has already been recorded as complete. This puts the handshake under the request timeout instead of the connection timeout. Fixing phase-local deadline accounting would otherwise leave a connect-only configuration without a TLS handshake timeout. Complete each handshake in its connector using the connection timeout. Preserve native-tls transport errors and cover timeout propagation through both backends, including a successful handshake through a CONNECT tunnel.
Configuration menu - View commit details
-
Copy full SHA for d480543 - Browse repository at this point
Copy the full SHA d480543View commit details -
Anchor timeout budgets to phase boundaries (#1194)
* Anchor timeout budgets to phase boundaries Each completed phase's deadline stayed in the set of timeouts checked by the phases after it, so for instance timeout_recv_response kept applying while the response body was read. The active phase also restarted its budget on every lookup, so repeated reads or writes renewed the timeout_send_body and timeout_recv_body budgets indefinitely. Anchor each phase's budget to the completion of its latest predecessor and check only that deadline together with the global and per-call deadlines. Fail in Connection when a budget has already expired, since transports cannot set a zero socket timeout and would otherwise grant a short grace period per call. Cover phase expiry, optional phase transitions and global/per-call accounting across redirects with clock-based tests, and add a regression test for an expired body budget that runs both through the test transport and over real TCP.
Configuration menu - View commit details
-
Copy full SHA for 5b81318 - Browse repository at this point
Copy the full SHA 5b81318View commit details
Commits on Sep 6, 2026
-
Do not pool a connection with unconsumed input (#1198)
Connection::reuse probes the socket for bytes the server sent after the end of the body and drops the connection if it finds any. Harden that check by also checking the bytes already buffered. This is defense in-depth since connection pooling is bound by URL origin key, thus no cross contamination risk.
Configuration menu - View commit details
-
Copy full SHA for 9eb654c - Browse repository at this point
Copy the full SHA 9eb654cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9559d7b - Browse repository at this point
Copy the full SHA 9559d7bView commit details -
Configuration menu - View commit details
-
Copy full SHA for cf4a3cd - Browse repository at this point
Copy the full SHA cf4a3cdView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 3.4.0...3.4.1