curlopt_http_version(3) [mojave man page]

CURLOPT_HTTP_VERSION(3) 				     curl_easy_setopt options					   CURLOPT_HTTP_VERSION(3)

NAME

       CURLOPT_HTTP_VERSION - specify HTTP protocol version to use

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_HTTP_VERSION, long version);

DESCRIPTION

       Pass  version a long, set to one of the values described below. They ask libcurl to use the specific HTTP versions. This is not sensible to
       do unless you have a good reason. You have to set this option if you want to use libcurl's HTTP/2 support.

       Note that the HTTP version is just a request. libcurl will still prioritize to re-use an existing connection so it might then re-use a con-
       nection using a HTTP version you haven't asked for.

       CURL_HTTP_VERSION_NONE
	      We don't care about what version the library uses. libcurl will use whatever it thinks fit.

       CURL_HTTP_VERSION_1_0
	      Enforce HTTP 1.0 requests.

       CURL_HTTP_VERSION_1_1
	      Enforce HTTP 1.1 requests.

       CURL_HTTP_VERSION_2_0
	      Attempt HTTP 2 requests. libcurl will fall back to HTTP 1.1 if HTTP 2 can't be negotiated with the server. (Added in 7.33.0)

	      The alias CURL_HTTP_VERSION_2 was added in 7.43.0 to better reflect the actual protocol name.

       CURL_HTTP_VERSION_2TLS
	      Attempt  HTTP  2	over TLS (HTTPS) only. libcurl will fall back to HTTP 1.1 if HTTP 2 can't be negotiated with the HTTPS server. For
	      clear text HTTP servers, libcurl will use 1.1. (Added in 7.47.0)

       CURL_HTTP_VERSION_2_PRIOR_KNOWLEDGE
	      Issue non-TLS HTTP requests using HTTP/2 without HTTP/1.1 Upgrade. It requires prior  knowledge  that  the  server  supports  HTTP/2
	      straight away. HTTPS requests will still do HTTP/2 the standard way with negotiated protocol version in the TLS handshake. (Added in
	      7.49.0)

DEFAULT

       CURL_HTTP_VERSION_NONE

PROTOCOLS

       HTTP

EXAMPLE

       TODO

AVAILABILITY

       Along with HTTP

RETURN VALUE

       Returns CURLE_OK if HTTP is supported, and CURLE_UNKNOWN_OPTION if not.

SEE ALSO

       CURLOPT_SSLVERSION(3), CURLOPT_HTTP200ALIASES(3),

libcurl 7.54.0							   May 01, 2016 					   CURLOPT_HTTP_VERSION(3)

CURLMOPT_PIPELINING(3)					     curl_multi_setopt options					    CURLMOPT_PIPELINING(3)

NAME

       CURLMOPT_PIPELINING - enable HTTP pipelining and multiplexing

SYNOPSIS

       #include <curl/curl.h>

       CURLMcode curl_multi_setopt(CURLM *handle, CURLMOPT_PIPELINING, long bitmask);

DESCRIPTION

       Pass in the bitmask parameter to instruct libcurl to enable HTTP pipelining and/or HTTP/2 multiplexing for this multi handle.

       When enabled, libcurl will attempt to use those protocol features when doing parallel requests to the same hosts.

       For pipelining, this means that if you add a second request that can use an already existing connection, the second request will be "piped"
       on the same connection rather than being executed in parallel.

       For multiplexing, this means that follow-up requests can re-use an existing connection and send the new request multiplexed  over  that	at
       the same time as other transfers are already using that single connection.

       There  are  several  other  related options that are interesting to tweak and adjust to alter how libcurl spreads out requests on different
       connections or not etc.

       Before 7.43.0, this option was set to 1 and 0 to enable and disable HTTP/1.1 pipelining.

       Starting in 7.43.0, bitmask's second bit also has a meaning, and you can ask for pipelining and multiplexing independently of each other by
       toggling the correct bits.

       CURLPIPE_NOTHING
       Default, which means doing no attempts at pipelining or multiplexing.

       CURLPIPE_HTTP1
	If this bit is set, libcurl will try to pipeline HTTP/1.1 requests on connections that are already established and in use to hosts.

       CURLPIPE_MULTIPLEX
	 If this bit is set, libcurl will try to multiplex the new transfer over an existing connection if possible. This requires HTTP/2.

DEFAULT

       0 (both pipeline and multiplexing are off)

PROTOCOLS

       HTTP(S)

EXAMPLE

       TODO

AVAILABILITY

       Added in 7.16.0. Multiplex support bit added in 7.43.0.

RETURN VALUE

       Returns CURLM_OK if the option is supported, and CURLM_UNKNOWN_OPTION if not.

SEE ALSO

       CURLMOPT_MAX_PIPELINE_LENGTH(3), 	  CURLMOPT_PIPELINING_SITE_BL(3),	   CURLMOPT_CONTENT_LENGTH_PENALTY_SIZE(3),	     CURL-
       MOPT_CHUNK_LENGTH_PENALTY_SIZE(3), CURLMOPT_MAX_HOST_CONNECTIONS(3), CURLMOPT_MAXCONNECTS(3), CURLMOPT_MAX_HOST_CONNECTIONS(3),

libcurl 7.54.0							September 01, 2016					    CURLMOPT_PIPELINING(3)