conncache: only allow multiplexing within same multi handle #2152

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
1 participant
Owner

bagder commented Dec 5, 2017

Connections that are used for HTTP/1.1 Pipelining or HTTP/2 multiplexing
only get additional transfers added to them if the existing connection
is held by the same multi or easy handle. libcurl does not support doing
HTTP/2 streams in different threads using a shared connection.

conncache: only allow multiplexing within same multi handle
Connections that are used for HTTP/1.1 Pipelining or HTTP/2 multiplexing
only get additional transfers added to them if the existing connection
is held by the same multi or easy handle. libcurl does not support doing
HTTP/2 streams in different threads using a shared connection.

@bagder bagder closed this in ea3a5d0 Dec 5, 2017

@bagder bagder deleted the bagder/conncache-reuse-multiplex branch Dec 5, 2017

JohnDeHelian pushed a commit to JohnDeHelian/curl that referenced this pull request Dec 7, 2017

conncache: only allow multiplexing within same multi handle
Connections that are used for HTTP/1.1 Pipelining or HTTP/2 multiplexing
only get additional transfers added to them if the existing connection
is held by the same multi or easy handle. libcurl does not support doing
HTTP/2 streams in different threads using a shared connection.

Closes #2152
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment