Artifactspublic-v0

curl

master
ply4 git calls43 ms288 KiB3 cachedprotocol v2
83 lines2.2 KiBRaw

NAME

curl_multi_remove_handle - remove an easy handle from a multi session

SYNOPSIS

c
#include <curl/curl.h>

CURLMcode curl_multi_remove_handle(CURLM *multi_handle, CURL *easy_handle);

DESCRIPTION

Removes a given easy_handle from the multi_handle. This makes the specified easy handle be removed from this multi handle's control.

When the easy handle has been removed from a multi stack, it is again perfectly legal to invoke curl_easy_perform(3) on this easy handle.

Removing an easy handle while being in use is perfectly legal and effectively halts the transfer in progress involving that easy handle. All other easy handles and transfers remain unaffected.

It is fine to remove a handle at any time during a transfer, but not from within any libcurl callback function.

An internal handle, such as one passed to a CURLMOPT_NOTIFYFUNCTION(3) callback, cannot be removed and makes this function return CURLM_BAD_EASY_HANDLE.

Removing an easy handle from the multi handle before the corresponding transfer is complete might cause libcurl to close the connection - if the state of it and the internal protocol handler deem it necessary. Otherwise libcurl keeps the connection alive in the connection pool associated with the multi handle, ready to get reused for a future transfer using this multi handle.

%PROTOCOLS%

EXAMPLE

c
int main(void)
{
  CURLM *multi = curl_multi_init();
  int queued = 0;

  /* when an easy handle has completed, remove it */
  CURLMsg *msg = curl_multi_info_read(multi, &queued);
  if(msg) {
    if(msg->msg == CURLMSG_DONE) {
      /* a transfer ended */
      fprintf(stderr, "Transfer completed\n");
      curl_multi_remove_handle(multi, msg->easy_handle);
    }
  }
}

%AVAILABILITY%

RETURN VALUE

This function returns a CURLMcode indicating success or error.

CURLM_OK (0) means everything was OK, non-zero means an error occurred, see libcurl-errors(3).

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: curl_multi_remove_handle
5Section: 3
6Source: libcurl
7See-also:
8 - curl_multi_add_handle (3)
9 - curl_multi_cleanup (3)
10 - curl_multi_init (3)
11Protocol:
12 - All
13Added-in: 7.9.6
14---
16# NAME
18curl_multi_remove_handle - remove an easy handle from a multi session
20# SYNOPSIS
22~~~c
23#include <curl/curl.h>
25CURLMcode curl_multi_remove_handle(CURLM *multi_handle, CURL *easy_handle);
26~~~
28# DESCRIPTION
30Removes a given *easy_handle* from the *multi_handle*. This makes the
31specified easy handle be removed from this multi handle's control.
33When the easy handle has been removed from a multi stack, it is again
34perfectly legal to invoke curl_easy_perform(3) on this easy handle.
36Removing an easy handle while being in use is perfectly legal and effectively
37halts the transfer in progress involving that easy handle. All other easy
38handles and transfers remain unaffected.
40It is fine to remove a handle at any time during a transfer, but not from
41within any libcurl callback function.
43An internal handle, such as one passed to a CURLMOPT_NOTIFYFUNCTION(3)
44callback, cannot be removed and makes this function return
45CURLM_BAD_EASY_HANDLE.
47Removing an easy handle from the multi handle before the corresponding
48transfer is complete might cause libcurl to close the connection - if the
49state of it and the internal protocol handler deem it necessary. Otherwise
50libcurl keeps the connection alive in the connection pool associated with the
51multi handle, ready to get reused for a future transfer using this multi
52handle.
54# %PROTOCOLS%
56# EXAMPLE
58~~~c
59int main(void)
61 CURLM *multi = curl_multi_init();
62 int queued = 0;
64 /* when an easy handle has completed, remove it */
65 CURLMsg *msg = curl_multi_info_read(multi, &queued);
66 if(msg) {
67 if(msg->msg == CURLMSG_DONE) {
68 /* a transfer ended */
69 fprintf(stderr, "Transfer completed\n");
70 curl_multi_remove_handle(multi, msg->easy_handle);
71 }
72 }
74~~~
76# %AVAILABILITY%
78# RETURN VALUE
80This function returns a CURLMcode indicating success or error.
82CURLM_OK (0) means everything was OK, non-zero means an error occurred, see
83libcurl-errors(3).
Diagnostics4 git calls · 43 ms
CallStatusSizeTime043 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001.1 KiB · hit38 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=38
git.response.bytes=1170
git.response.cache=HIT
git.response.duration_ms=38
git.fetch.wants=a8ecdfec64c6462a7a6d9a2caa8364e52e376a8a
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1170
git.pkt.payload.max=1149
git.sideband.band1.bytes=1148
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e30771a89c15db
Request
4e3eee85…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format