Artifactspublic-v0

curl

master
ply4 git calls171 ms288 KiB2 cachedprotocol v2
88 lines2.6 KiBRaw

NAME

curl_easy_perform - perform a blocking network transfer

SYNOPSIS

c
#include <curl/curl.h>

CURLcode curl_easy_perform(CURL *easy_handle);

DESCRIPTION

curl_easy_perform(3) performs a network transfer in a blocking manner and returns when done, or earlier if it fails. For non-blocking behavior, see curl_multi_perform(3).

Invoke this function after curl_easy_init(3) and all the curl_easy_setopt(3) calls are made, and it performs the transfer as described in the options. It must be called with the same easy_handle as input as the curl_easy_init(3) call returned.

You can do any amount of calls to curl_easy_perform(3) while using the same easy_handle. If you intend to transfer more than one file, you are even encouraged to do so. libcurl attempts to reuse existing connections for the following transfers, thus making the operations faster, less CPU intense and using less network resources. You probably want to use curl_easy_setopt(3) between the invokes to set options for the following curl_easy_perform(3) call.

You must never call this function simultaneously from two places using the same easy_handle. Let the function return first before invoking it another time. If you want parallel transfers, you must use several curl easy_handles.

A network transfer moves data to a peer or from a peer. An application tells libcurl how to receive data by setting the CURLOPT_WRITEFUNCTION(3) and CURLOPT_WRITEDATA(3) options. To tell libcurl what data to send, there are a few more alternatives but two common ones are CURLOPT_READFUNCTION(3) and CURLOPT_POSTFIELDS(3).

While the easy_handle is added to a multi handle, it cannot be used by curl_easy_perform(3).

%PROTOCOLS%

EXAMPLE

c
int main(void)
{
  CURL *curl = curl_easy_init();
  if(curl) {
    CURLcode result;
    curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
    result = curl_easy_perform(curl);
    curl_easy_cleanup(curl);
  }
}

%AVAILABILITY%

RETURN VALUE

This function returns a CURLcode indicating success or error.

CURLE_OK (0) means everything was OK, non-zero means an error occurred, see libcurl-errors(3). If CURLOPT_ERRORBUFFER(3) was set with curl_easy_setopt(3) there can be an error message stored in the error buffer when non-zero is returned.

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Title: curl_easy_perform
5Section: 3
6Source: libcurl
7See-also:
8 - curl_easy_init (3)
9 - curl_easy_setopt (3)
10 - curl_multi_add_handle (3)
11 - curl_multi_perform (3)
12 - libcurl-errors (3)
13Protocol:
14 - All
15Added-in: 7.1
16---
18# NAME
20curl_easy_perform - perform a blocking network transfer
22# SYNOPSIS
24~~~c
25#include <curl/curl.h>
27CURLcode curl_easy_perform(CURL *easy_handle);
28~~~
30# DESCRIPTION
32curl_easy_perform(3) performs a network transfer in a blocking manner and
33returns when done, or earlier if it fails. For non-blocking behavior, see
34curl_multi_perform(3).
36Invoke this function after curl_easy_init(3) and all the curl_easy_setopt(3)
37calls are made, and it performs the transfer as described in the options. It
38must be called with the same **easy_handle** as input as the curl_easy_init(3)
39call returned.
41You can do any amount of calls to curl_easy_perform(3) while using the same
42**easy_handle**. If you intend to transfer more than one file, you are even
43encouraged to do so. libcurl attempts to reuse existing connections for the
44following transfers, thus making the operations faster, less CPU intense and
45using less network resources. You probably want to use curl_easy_setopt(3)
46between the invokes to set options for the following curl_easy_perform(3)
47call.
49You must never call this function simultaneously from two places using the
50same **easy_handle**. Let the function return first before invoking it another
51time. If you want parallel transfers, you must use several curl easy_handles.
53A network transfer moves data to a peer or from a peer. An application tells
54libcurl how to receive data by setting the CURLOPT_WRITEFUNCTION(3) and
55CURLOPT_WRITEDATA(3) options. To tell libcurl what data to send, there are a
56few more alternatives but two common ones are CURLOPT_READFUNCTION(3) and
57CURLOPT_POSTFIELDS(3).
59While the **easy_handle** is added to a multi handle, it cannot be used by
60curl_easy_perform(3).
62# %PROTOCOLS%
64# EXAMPLE
66~~~c
67int main(void)
69 CURL *curl = curl_easy_init();
70 if(curl) {
71 CURLcode result;
72 curl_easy_setopt(curl, CURLOPT_URL, "https://example.com");
73 result = curl_easy_perform(curl);
74 curl_easy_cleanup(curl);
75 }
77~~~
79# %AVAILABILITY%
81# RETURN VALUE
83This function returns a CURLcode indicating success or error.
85CURLE_OK (0) means everything was OK, non-zero means an error occurred, see
86libcurl-errors(3). If CURLOPT_ERRORBUFFER(3) was set with curl_easy_setopt(3)
87there can be an error message stored in the error buffer when non-zero is
88returned.
Diagnostics4 git calls · 171 ms
CallStatusSizeTime0171 ms
discover200152 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
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 · hit2 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=2
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=2
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 · hit4 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=4
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.3 KiB165 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=165
git.response.bytes=1327
git.response.cache=MISS
git.response.duration_ms=165
git.fetch.wants=cc61232f875c2e359b9dce9892869b6677e2b358
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=1327
git.pkt.payload.max=1306
git.sideband.band1.bytes=1305
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
a5e3497f9dfa4652
Request
adca7e8b…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format