Deps

• h1-client now uses dashmap at version 5.x >, fixing an unsoundness issue.

Deps

• Now only uses dashmap for h1-client.

Same as 6.5.0 with one change:

Config::max_connections_per_host() is now properly named Config::set_max_connections_per_host().

Added

• Config has been stabilized and is now available by default!
• wasm_client support for Config (only timeouts).
• Config::max_connections_per_host (Supported on h1_client and curl_client.)

Deprecated

• H1Client::with_max_connections() will be superseded by Config::max_connections_per_host.

(Yanked)

Added

• Config has been stabilized and is now available by default!
• wasm_client support for Config (only timeouts).
• Config::max_connections_per_host (Supported on h1_client and curl_client.)

Deprecated

• H1Client::with_max_connections() will be superseded by Config::max_connections_per_host.

Docs

• Added "unstable-config" to the docs builds.

Added

• Added a new unstable-config feature, which exposes runtime configuration via a new Config struct.

Fixed

• Multiple headers of the same name are now present with any client backend and not just h1_client.
• Connection when multiple IPs are present for a hostname not function with the h1_client backend.

Fixed

• h1_client connection pools now properly check if connections are still alive before recycling them.
  • Like, actually properly this time.
  • There is a test now to ensure closed connections don't cause errors.

Fixed

• h1_client connection pools now properly check if connections are still alive before recycling them.

Fixed

• Allow http-client to build & run properly when h1_client is enabled without either tls option.
• Prefer rustls if both tls features are enabled.

Internal

• More exhaustive CI for feature combinations.