From 568037f6af69c52fb1796a147eb18d6eb5638f0d Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Thu, 27 Oct 2016 23:15:12 -0400 Subject: [PATCH] CURLMOPT_MAX_PIPELINE_LENGTH.3: Clarify it's not for HTTP/2 - Clarify that this option is only for HTTP/1.1 pipelining. Bug: https://github.com/curl/curl/issues/1059 Reported-by: Jeroen Ooms Assisted-by: Daniel Stenberg --- docs/libcurl/opts/CURLMOPT_MAX_PIPELINE_LENGTH.3 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/libcurl/opts/CURLMOPT_MAX_PIPELINE_LENGTH.3 b/docs/libcurl/opts/CURLMOPT_MAX_PIPELINE_LENGTH.3 index cac3c7193..1204a0f9d 100644 --- a/docs/libcurl/opts/CURLMOPT_MAX_PIPELINE_LENGTH.3 +++ b/docs/libcurl/opts/CURLMOPT_MAX_PIPELINE_LENGTH.3 @@ -29,8 +29,8 @@ CURLMOPT_MAX_PIPELINE_LENGTH \- maximum number of requests in a pipeline CURLMcode curl_multi_setopt(CURLM *handle, CURLMOPT_MAX_PIPELINE_LENGTH, long max); .SH DESCRIPTION Pass a long. The set \fBmax\fP number will be used as the maximum amount of -outstanding requests in a pipelined connection. Only used if pipelining is -enabled. +outstanding requests in an HTTP/1.1 pipelined connection. This option is only +used for HTTP/1.1 pipelining, not for HTTP/2 multiplexing. When this limit is reached, libcurl will use another connection to the same host (see \fICURLMOPT_MAX_HOST_CONNECTIONS(3)\fP), or queue the request until