Artifactspublic-v0

curl

master
ply4 git calls325 ms290 KiB2 cachedprotocol v2
203 lines6.2 KiBRaw

EXIT CODES

There are a bunch of different error codes and their corresponding error messages that may appear under error conditions. At the time of this writing, the exit codes are:

0

Success. The operation completed successfully according to the instructions.

1

Unsupported protocol. This build of curl has no support for this protocol.

2

Failed to initialize.

3

URL malformed. The syntax was not correct.

4

A feature or option that was needed to perform the desired request was not enabled or was explicitly disabled at build-time. To make curl able to do this, you probably need another build of libcurl.

5

Could not resolve proxy. The given proxy host could not be resolved.

6

Could not resolve host. The given remote host could not be resolved.

7

Failed to connect to host.

8

Weird server reply. The server sent data curl could not parse.

9

FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that does not exist on the server.

10

FTP accept failed. While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.

11

FTP weird PASS reply. curl could not parse the reply sent to the PASS request.

12

During an active FTP session while waiting for the server to connect back to curl, the timeout expired.

13

FTP weird PASV reply, curl could not parse the reply sent to the PASV request.

14

FTP weird 227 format. curl could not parse the 227-line the server sent.

15

FTP cannot use host. Could not resolve the host IP we got in the 227-line.

16

HTTP/2 error. A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error message for details.

17

FTP could not set binary. Could not change transfer method to binary.

18

Partial file. Only a part of the file was transferred.

19

FTP could not download/access the given file, the RETR (or similar) command failed.

21

FTP quote error. A quote command returned error from the server.

22

HTTP page not retrieved. The requested URL was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if --fail is used.

23

Write error. curl could not write data to a local file system or similar.

25

Failed starting the upload. For FTP, the server typically denied the STOR command.

26

Read error. Various reading problems.

27

Out of memory. A memory allocation request failed.

28

Operation timeout. The specified time-out period was reached according to the conditions.

30

FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT command, try doing a transfer using PASV instead.

31

FTP could not use REST. The REST command failed. This command is used for resumed FTP transfers.

33

HTTP range error. The range "command" did not work.

34

HTTP post error. Internal post-request generation error.

35

SSL connect error. The SSL handshaking failed.

36

Bad download resume. Could not continue an earlier aborted download.

37

FILE could not read file. Failed to open the file. Permissions?

38

LDAP cannot bind. LDAP bind operation failed.

39

LDAP search failed.

41

Function not found. A required LDAP function was not found.

42

Aborted by callback. An application told curl to abort the operation.

43

Internal error. A function was called with a bad parameter.

45

Interface error. A specified outgoing interface could not be used.

47

Too many redirects. When following redirects, curl hit the maximum amount.

48

Unknown option specified to libcurl. This indicates that you passed a weird option to curl that was passed on to libcurl and rejected. Read up in the manual.

49

Malformed telnet option.

52

The server did not reply anything, which here is considered an error.

53

SSL crypto engine not found.

54

Cannot set SSL crypto engine as default.

55

Failed sending network data.

56

Failure in receiving network data.

58

Problem with the local certificate.

59

Could not use specified SSL cipher.

60

Peer certificate cannot be authenticated with known CA certificates.

61

Unrecognized transfer encoding.

63

Maximum file size exceeded.

64

Requested FTP SSL level failed.

65

Sending the data requires a rewind that failed.

66

Failed to initialize SSL Engine.

67

The username, password, or similar was not accepted and curl failed to log in.

68

File not found on TFTP server.

69

Permission problem on TFTP server.

70

Out of disk space on TFTP server.

71

Illegal TFTP operation.

72

Unknown TFTP transfer ID.

73

File already exists (TFTP).

74

No such user (TFTP).

77

Problem reading the SSL CA cert (path? access rights?).

78

The resource referenced in the URL does not exist.

79

An unspecified error occurred during the SSH session.

80

Failed to shut down the SSL connection.

82

Could not load CRL file, missing or wrong format (added in 7.19.0).

83

Issuer check failed (added in 7.19.0).

84

The FTP PRET command failed.

85

Mismatch of RTSP CSeq numbers.

86

Mismatch of RTSP Session Identifiers.

87

Unable to parse FTP file list.

88

FTP chunk callback reported error.

89

No connection available, the session is queued.

90

SSL public key does not match pinned public key.

91

Invalid SSL certificate status.

92

Stream error in HTTP/2 framing layer.

93

An API function was called from inside a callback.

94

An authentication function returned an error.

95

A problem was detected in the HTTP/3 layer. This is somewhat generic and can be one out of several problems, see the error message for details.

96

QUIC connection error. This error may be caused by an SSL library error. QUIC is the protocol used for HTTP/3 transfers.

97

Proxy handshake error.

98

A client-side certificate is required to complete the TLS handshake.

99

Poll or select returned fatal error.

100

A value or data field grew larger than allowed.

XX

More error codes might appear here in future releases. The existing ones are meant to never change.

1<!-- Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al. -->
2<!-- SPDX-License-Identifier: curl -->
3# EXIT CODES
4There are a bunch of different error codes and their corresponding error
5messages that may appear under error conditions. At the time of this writing,
6the exit codes are:
7## 0
8Success. The operation completed successfully according to the instructions.
9## 1
10Unsupported protocol. This build of curl has no support for this protocol.
11## 2
12Failed to initialize.
13## 3
14URL malformed. The syntax was not correct.
15## 4
16A feature or option that was needed to perform the desired request was not
17enabled or was explicitly disabled at build-time. To make curl able to do
18this, you probably need another build of libcurl.
19## 5
20Could not resolve proxy. The given proxy host could not be resolved.
21## 6
22Could not resolve host. The given remote host could not be resolved.
23## 7
24Failed to connect to host.
25## 8
26Weird server reply. The server sent data curl could not parse.
27## 9
28FTP access denied. The server denied login or denied access to the particular
29resource or directory you wanted to reach. Most often you tried to change to a
30directory that does not exist on the server.
31## 10
32FTP accept failed. While waiting for the server to connect back when an active
33FTP session is used, an error code was sent over the control connection or
34similar.
35## 11
36FTP weird PASS reply. curl could not parse the reply sent to the PASS request.
37## 12
38During an active FTP session while waiting for the server to connect back to
39curl, the timeout expired.
40## 13
41FTP weird PASV reply, curl could not parse the reply sent to the PASV request.
42## 14
43FTP weird 227 format. curl could not parse the 227-line the server sent.
44## 15
45FTP cannot use host. Could not resolve the host IP we got in the 227-line.
46## 16
47HTTP/2 error. A problem was detected in the HTTP2 framing layer. This is
48somewhat generic and can be one out of several problems, see the error message
49for details.
50## 17
51FTP could not set binary. Could not change transfer method to binary.
52## 18
53Partial file. Only a part of the file was transferred.
54## 19
55FTP could not download/access the given file, the RETR (or similar) command
56failed.
57## 21
58FTP quote error. A quote command returned error from the server.
59## 22
60HTTP page not retrieved. The requested URL was not found or returned another
61error with the HTTP error code being 400 or above. This return code only
62appears if --fail is used.
63## 23
64Write error. curl could not write data to a local file system or similar.
65## 25
66Failed starting the upload. For FTP, the server typically denied the STOR
67command.
68## 26
69Read error. Various reading problems.
70## 27
71Out of memory. A memory allocation request failed.
72## 28
73Operation timeout. The specified time-out period was reached according to the
74conditions.
75## 30
76FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT
77command, try doing a transfer using PASV instead.
78## 31
79FTP could not use REST. The REST command failed. This command is used for
80resumed FTP transfers.
81## 33
82HTTP range error. The range "command" did not work.
83## 34
84HTTP post error. Internal post-request generation error.
85## 35
86SSL connect error. The SSL handshaking failed.
87## 36
88Bad download resume. Could not continue an earlier aborted download.
89## 37
90FILE could not read file. Failed to open the file. Permissions?
91## 38
92LDAP cannot bind. LDAP bind operation failed.
93## 39
94LDAP search failed.
95## 41
96Function not found. A required LDAP function was not found.
97## 42
98Aborted by callback. An application told curl to abort the operation.
99## 43
100Internal error. A function was called with a bad parameter.
101## 45
102Interface error. A specified outgoing interface could not be used.
103## 47
104Too many redirects. When following redirects, curl hit the maximum amount.
105## 48
106Unknown option specified to libcurl. This indicates that you passed a weird
107option to curl that was passed on to libcurl and rejected. Read up in the
108manual.
109## 49
110Malformed telnet option.
111## 52
112The server did not reply anything, which here is considered an error.
113## 53
114SSL crypto engine not found.
115## 54
116Cannot set SSL crypto engine as default.
117## 55
118Failed sending network data.
119## 56
120Failure in receiving network data.
121## 58
122Problem with the local certificate.
123## 59
124Could not use specified SSL cipher.
125## 60
126Peer certificate cannot be authenticated with known CA certificates.
127## 61
128Unrecognized transfer encoding.
129## 63
130Maximum file size exceeded.
131## 64
132Requested FTP SSL level failed.
133## 65
134Sending the data requires a rewind that failed.
135## 66
136Failed to initialize SSL Engine.
137## 67
138The username, password, or similar was not accepted and curl failed to log in.
139## 68
140File not found on TFTP server.
141## 69
142Permission problem on TFTP server.
143## 70
144Out of disk space on TFTP server.
145## 71
146Illegal TFTP operation.
147## 72
148Unknown TFTP transfer ID.
149## 73
150File already exists (TFTP).
151## 74
152No such user (TFTP).
153## 77
154Problem reading the SSL CA cert (path? access rights?).
155## 78
156The resource referenced in the URL does not exist.
157## 79
158An unspecified error occurred during the SSH session.
159## 80
160Failed to shut down the SSL connection.
161## 82
162Could not load CRL file, missing or wrong format (added in 7.19.0).
163## 83
164Issuer check failed (added in 7.19.0).
165## 84
166The FTP PRET command failed.
167## 85
168Mismatch of RTSP CSeq numbers.
169## 86
170Mismatch of RTSP Session Identifiers.
171## 87
172Unable to parse FTP file list.
173## 88
174FTP chunk callback reported error.
175## 89
176No connection available, the session is queued.
177## 90
178SSL public key does not match pinned public key.
179## 91
180Invalid SSL certificate status.
181## 92
182Stream error in HTTP/2 framing layer.
183## 93
184An API function was called from inside a callback.
185## 94
186An authentication function returned an error.
187## 95
188A problem was detected in the HTTP/3 layer. This is somewhat generic and can
189be one out of several problems, see the error message for details.
190## 96
191QUIC connection error. This error may be caused by an SSL library error. QUIC
192is the protocol used for HTTP/3 transfers.
193## 97
194Proxy handshake error.
195## 98
196A client-side certificate is required to complete the TLS handshake.
197## 99
198Poll or select returned fatal error.
199## 100
200A value or data field grew larger than allowed.
201## XX
202More error codes might appear here in future releases. The existing ones are
203meant to never change.
Diagnostics4 git calls · 325 ms
CallStatusSizeTime0325 ms
discover200152 B2 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
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 · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=321
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
fetch2002.7 KiB321 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=2804
git.response.cache=MISS
git.response.duration_ms=321
git.fetch.wants=333e198d7c729e75e5a7073289f08bdae954d73d
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=2804
git.pkt.payload.max=2783
git.sideband.band1.bytes=2782
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
a5e3246abc6898f1
Request
046ff726…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format