async-http-client
async-http-client copied to clipboard
swift-server
HTTP client library built on SwiftNIO
for debugging purposes, we should offer an option to switch on plain text .pcap recording. It should be very clear that it's for debugging because `NIOWritePCAPHandler.SynchronisedFileSink` blocks the event loop...
While refactoring the unix domain socket implementation in #228, I noticed that we could probably combine the `host` and (new) `socketPath` properties on `HTTPClient.Request`. From what I could tell: -...
This is quite a minor issue but `redirectConfiguration` sticks out: ``` public init(tlsConfiguration: TLSConfiguration? = nil, redirectConfiguration: RedirectConfiguration? = nil, timeout: Timeout = Timeout(), proxy: Proxy? = nil, ignoreUncleanSSLShutdown: Bool...
In order for other Cocoapod-enabled packages to adopt this one (such as [SwiftyRequest](https://github.com/IBM-Swift/SwiftyRequest/pull/76)), an async-http-client pod is needed. Swift-NIO et. al is already available in pod form, so I believe...
I wonder if when [function builders](https://github.com/apple/swift-evolution/blob/9992cf3c11c2d5e0ea20bee98657d93902d5b174/proposals/XXXX-function-builders.md) have formally been added to Swift a declarative API with function builders could be made akin to this library: https://github.com/carson-katri/swift-request
### Motivation In integration tests we often want to inspect the connection error thrown during connection establishment for a request. Currently the only way to get at the connection error...
Offer `HTTPClient.shared`, a global singleton `HTTPClient` that doesn't need shutdown (because it lives as long as your application). This globally shared `HTTPClient` does not accept any special configuration and uses...
Motivation: In several examples of async/await support, the call to shutdown() on the HTTPClient are made with await but do not call get() on the EventLoopFuture. Modifications: Add the .get()...
Sadly `HTTPClientRequest` contains a streamable body which is typically a reference to a (frequently) consume-once `AsyncSequence`. That means it's not actually a value type. That's a major API winkle that...
After executing a request via HTTP2 and then calling shutdown the connection to the server is left open. I would expect shutdown to close any open connections.
