Re: Pipelining in HTTP 1.1

2020-10-01 Thread Daniel Stenberg via curl-library
On Thu, 1 Oct 2020, Dorit Mari via curl-library wrote: I know that support for pipelining in HTTP 1.1 was removed (https://github.com/curl/curl/commit/2f44e94efb3df8e50bb2ddbc4ec6b569a6424517). In our application, we need to use pipelining in HTTP 1.1, so we are trying to restore and fix the

Pipelining in HTTP 1.1

2020-10-01 Thread Dorit Mari via curl-library
Hello, I know that support for pipelining in HTTP 1.1 was removed (https://github.com/curl/curl/commit/2f44e94efb3df8e50bb2ddbc4ec6b569a6424517). In our application, we need to use pipelining in HTTP 1.1, so we are trying to restore and fix the pipelining support in libcurl. In the commit that

Re: Can Curl round-robin IP addresses for successive connects?

2020-10-01 Thread Rainer Canavan via curl-library
On Thu, Oct 1, 2020 at 6:36 PM Jason Proctor via curl-library wrote: > > Dear Curl, > > Our application pulls resources from CloudFront and we noticed some > significant bandwidth capping. Turns out that for maximum throughput, > Amazon recommend requests be spread across the IP addresses

Can Curl round-robin IP addresses for successive connects?

2020-10-01 Thread Jason Proctor via curl-library
Dear Curl, Our application pulls resources from CloudFront and we noticed some significant bandwidth capping. Turns out that for maximum throughput, Amazon recommend requests be spread across the IP addresses returned by the DNS call. However from looking at Curl_connecthost() and related