async-http-client icon indicating copy to clipboard operation
async-http-client copied to clipboard

HTTP client library built on SwiftNIO

Results 139 async-http-client issues
Sort by recently updated
recently updated
newest added

See [here](https://karwa.github.io/swift-url/0.3.1/documentation/weburl/foundationinterop/#URL-Strings-are-Ambiguous) for more information. In short: URL strings are ambiguous. IMO, APIs which accept a URL as a string should be deprecated, and replaced with APIs accepting a parsed...

There are use-cases where the target server can handle more concurrent requests than its `MAX_CONCURRENT_STREAMS` HTTP/2 setting. This is especially often the case behind load balancers which may just pick...

kind/enhancement

For best bulk transfer rates, it'd be great to control the HTTP/2 flow control window. Right now, I think we leave the defaults which are (IIRC) 64k per connection and...

kind/enhancement

AsyncHTTPClient commit hash: > ec2e080d7011a81bd67f10bf41efe6104d7799d6 Swift Version: > swift-driver version: 1.26.21 Apple Swift version 5.5.2 (swiftlang-1300.0.47.5 clang-1300.0.29.30) > Target: x86_64-apple-macosx12.0 ## Context We have a Vapor 4 project that has...

Failed on Swift 5.2 CI: https://ci.swiftserver.group/job/async-http-client-swift52-prb/1008/console ``` Test Case 'HTTPClientTests.testConnectionPoolSizeConfigValueIsRespected' started at 2021-11-25 17:33:23.508 /code/Tests/AsyncHTTPClientTests/HTTPClientTests.swift:2971: error: HTTPClientTests.testConnectionPoolSizeConfigValueIsRespected : failed - Timed out /code/Tests/AsyncHTTPClientTests/HTTPClientTests.swift:2959: error: HTTPClientTests.testConnectionPoolSizeConfigValueIsRespected : XCTAssertNoThrow failed: threw error...

area/testing

Also remove an unneeded NIOFoundationCompat target dependency (it's only used by tests, not the AHC library itself). NIOTS also has an unconditional target dependency on NIOFoundationCompat. In the WebURL port,...

I am trying to read the header of a request that gets redirected. However it seems that the callback is is never called after the redirect. The new request has...