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

I’m looking to specify a local address when sending requests with async-http-client, but I don’t see a direct option for this. Is there a workaround or a way to achieve...

We have a mTLS proxy server in DMZ, and client applications with auth certificate can send requests to private network through it. Currently I using iOS 17.0+ api: ProxyConfiguration.init( httpCONNECTProxy:...

For some reason, HTTPClient hides the configuration that was used to configure it from the user. We shouldn't do that.

I know that there is the capability to specify an `HTTPClient.Configuration.Proxy` configuration that accepts a `host`, `port`, and `authorization` set of properties of a single server. But I'm wondering if,...

I improperly created a PR off my fork's `main` and not the right branch. This is a successor to #553 1. Added examples for HTTP POST 2. Added README for...

Another big bump in a transition from `URLSession` to `HTTPClient`: HTTPClient has no way of knowing the internet is offline or is disconnected. An executed request that hasn't connected will...

If I create a HTTPClient as follows ```swift let httpClient = HTTPClient( eventLoopGroup: MultiThreadedEventLoopGroup.singleton, configuration: .init(timeout: Timeout(read: .seconds(90)) ) ``` and then call ``` let response = httpClient(request, timeout: .minutes(10),...

kind/bug

Am I correct that to track the progress of sent data, you need to use a delegate? And further, I would need to use futures to use the delegate? I...

[Swift HTTP Types](https://github.com/apple/swift-http-types) is an agnostic package describing basic HTTP types. As we further adopt Swift Concurrency, and therefore make NIO an implementation detail, we should offer APIs that use...

kind/feature

As mentioned in the Workflow Approval docs: https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-public-forks > By default, all first-time contributors require approval to run workflows. I think this default behavior is great and makes sense! Please...