Cory BenfieldandGitHub e294c8f28f Accurately apply the connect timeout in async code (#616) ...

Motivation

We should apply the connect timeout to the complete set of connection
attempts, rather than the request deadline. This allows users
fine-grained control over how long we attempt to connect for. This is
also the behaviour of our old-school interface.

Modifications

- Changed the connect deadline calculation for async/await to match that
  of the future-based code.
- Added a connect timeout test.

Result

Connect timeouts are properly handled

2022-08-16 13:17:45 +01:00

..

HTTPClient+execute.swift

Accurately apply the connect timeout in async code (#616)

2022-08-16 13:17:45 +01:00

HTTPClient+shutdown.swift

Make async/await API public (#552)

2022-02-08 11:48:58 +01:00

HTTPClientRequest.swift

Use Docc for documentation (#613)

2022-08-09 16:23:14 +01:00

HTTPClientRequest+Prepared.swift

Prepare async/await API for public release (#531)

2022-01-14 14:35:17 +01:00

HTTPClientResponse.swift

Use Docc for documentation (#613)

2022-08-09 16:23:14 +01:00

Transaction.swift

Report last connection error if request deadline is exceeded with async/await API (#608)

2022-08-04 18:24:34 +02:00

Transaction+StateMachine.swift

Report last connection error if request deadline is exceeded with async/await API (#608)

2022-08-04 18:24:34 +02:00