Skip to content

v1.1.7

Choose a tag to compare

View all tags
@oznetmaster oznetmaster released this 13 Jul 08:42
v1.1.7
9064dc0

Fixes KlapTransport not honoring the configured DeviceConfiguration.Timeout on .NET 10.

The non-net472 request path in KlapTransport (used for KLAP handshake and encrypted requests) called the shared static HttpClient.SendAsync using only whatever CancellationToken the caller supplied, with no per-call deadline derived from DeviceConfiguration.Timeout -- unlike the net472 HttpWebRequest fallback (which sets request.Timeout/ReadWriteTimeout) and TpapTransport (which wraps every request in a per-call timeout via CreateOperationTimeoutSource). Because the shared HttpClient itself has no Timeout configured, a caller that did not supply its own deadline (e.g. CancellationToken.None) would silently fall back to the .NET runtime's default HttpClient timeout of about 100 seconds instead of the configured value.

KlapTransport now wraps every non-net472 request with a per-call timeout derived from DeviceConfiguration.Timeout, matching the behavior already present in TpapTransport and the net472 KLAP fallback. This completes coverage of the originally reported issue: none of the three transports (KLAP, TPAP, Legacy) now silently ignore the caller-configured Timeout on any supported target framework.

Full Changelog: v1.1.6...v1.1.7

Assets 6
Loading