Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: CURLPIPE_MULTIPLEX option for http1.1 and 2.0
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Fri, 31 May 2019 22:51:52 +0200 (CEST)
Date: Fri, 31 May 2019 22:51:52 +0200 (CEST)
On Sat, 1 Jun 2019, Kunal Ekawde via curl-library wrote:
> If we have both HTTP/1.1 and HTTP/2.0 transfers happening over same multi
> handle (can it not ?) ,
Yes it can.
> can we safely set CURLPIPE_MULTIPLEX for CURLMOPT_PIPELINING.
Yes you can.
> We don't want to have HTTP1.1 pipelining but need HTTP/2 multiplexing.Since
> multi handle is same, wont setting the CURLPIPE_MULTIPLEX option impact
> both HTTP1.1 & HTTP/2 transfers ?
There's no multiplexing in HTTP/1 so it could only do multiplexing for those
requests and connections that negotiate HTTP/2.
But yes, it is a boolean switch that applies the all handles/transfers done
with that multi handle.
--
/ daniel.haxx.se | Get the best commercial curl support there is - from me
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-05-31