Skip to content
Permalink

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.1
Choose a base ref
...
head repository: algesten/ureq
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.4.2
Choose a head ref
  • 4 commits
  • 8 files changed
  • 3 contributors

Commits on Sep 10, 2026

  1. Try the next resolved address when a connect fails for that address o…

    …nly (#1195)
    
    ## Summary
    
    Try the next resolved address when TCP connect fails with ConnectionRefused, HostUnreachable, NetworkUnreachable, or AddrNotAvailable. This allows a reachable address to succeed when an earlier address has no usable route, such as IPv6 on a host with only IPv4 connectivity.
    
    On Windows, also retry WSAEACCES (10013) for the VPN/address-family failure reported in #1184. Rust maps this code to PermissionDenied; matching the raw OS code keeps the exception specific to this socket error.
    
    When all addresses fail, return the last connection failure, including per-address timeouts, instead of a synthesized refusal or an earlier address's I/O error. An expired overall deadline retains its configured timeout reason. Add deterministic tests for fallback, error ordering, timeout precedence, and early termination, alongside error-classification tests.
    
    Fixes #1184.
    
    Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
    Co-Authored-By: Martin Algesten <martin@algesten.se>
    3 people authored Sep 10, 2026
    Configuration menu
    Copy the full SHA
    fb634de View commit details
    Browse the repository at this point in the history

Commits on Sep 13, 2026

  1. Respect request connection settings when pooling

    ## Summary
    
    Bypass Agent pool lookup and return when a request's connection settings are incompatible with the Agent configuration. This prevents request-level TLS identities and other connection overrides from borrowing or populating the Agent's pool, while preserving reuse for compatible requests.
    
    Use exhaustive destructuring of Config and TlsConfig so every added field requires an explicit pooling decision. Compare TLS credentials, explicit root sets, and custom crypto providers by shared identity; cloned settings remain compatible. Proxy settings remain separated by the existing pool key, and request-only settings do not disable pooling.
    algesten authored Sep 13, 2026
    Configuration menu
    Copy the full SHA
    075a1d7 View commit details
    Browse the repository at this point in the history
  2. Bump ureq-proto to 0.6.3

    algesten committed Sep 13, 2026
    Configuration menu
    Copy the full SHA
    b983841 View commit details
    Browse the repository at this point in the history
  3. 3.4.2

    algesten committed Sep 13, 2026
    Configuration menu
    Copy the full SHA
    2e9ef24 View commit details
    Browse the repository at this point in the history
Loading