Artifactspublic-v0

curl

master
ply4 git calls28 ms288 KiB3 cachedprotocol v2
81 lines2.3 KiBRaw

--verbose

Make curl output verbose information during the operation. Useful for debugging and seeing what's going on under the hood. Verbose output lines are prefixed with letters:

>

header sent by curl

<

header received by curl

}

data sent by curl

{

data received by curl

*

additional info provided by curl. Text that adds explanations what goes on and about choices curl does.

If you only want HTTP headers in the output, --show-headers or --dump-header might be more suitable options.

Since curl 8.10, mentioning this option several times in the same argument increases the level of the trace output. As before, a single --verbose or --no-verbose reverts any additions by previous -vv again. This means that -vv -v is equivalent to a single -v. This avoids unwanted verbosity when the option is mentioned in the command line and curl config files.

Using it twice, e.g. -vv, outputs time (--trace-time) and transfer ids (--trace-ids), as well as enabling tracing for all protocols (--trace-config protocol).

Adding a third verbose outputs transfer content (--trace-ascii %) and enables tracing of more components (--trace-config read,write,ssl).

A fourth time adds tracing of all network components. (--trace-config network).

Any addition of the verbose option after that has no effect.

If you think this option does not give you the right details, consider using --trace or --trace-ascii instead. Or use it only once and use --trace-config to trace the specific components you wish to see.

Note that verbose output of curl activities and network traffic might contain sensitive data, including usernames, credentials or secret data content. Be aware and be careful when sharing trace logs with others.

When the output contains protocol headers, those lines might include carriage return (ASCII code 13) characters, even on platforms that otherwise normally only use linefeed to signify line separations - as curl shows the exact contents arriving from the server.

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Short: v
5Long: verbose
6Mutexed: trace trace-ascii
7Help: Make the operation more talkative
8Category: important verbose global
9Added: 4.0
10Multi: boolean
11Scope: global
12See-also:
13 - show-headers
14 - silent
15 - trace
16 - trace-ascii
17Example:
18 - --verbose $URL
19---
21# `--verbose`
23Make curl output verbose information during the operation. Useful for
24debugging and seeing what's going on under the hood. Verbose output lines are
25prefixed with letters:
27## >
29header sent by curl
31## <
33header received by curl
35## }
37data sent by curl
39## {
41data received by curl
43## *
45additional info provided by curl. Text that adds explanations what goes on and
46about choices curl does.
48##
50If you only want HTTP headers in the output, --show-headers or --dump-header
51might be more suitable options.
53Since curl 8.10, mentioning this option several times in the same argument
54increases the level of the trace output. As before, a single --verbose or
55--no-verbose reverts any additions by previous `-vv` again. This means that
56`-vv -v` is equivalent to a single -v. This avoids unwanted verbosity when the
57option is mentioned in the command line *and* curl config files.
59Using it twice, e.g. `-vv`, outputs time (--trace-time) and transfer ids
60(--trace-ids), as well as enabling tracing for all protocols (--trace-config
61protocol).
63Adding a third verbose outputs transfer content (--trace-ascii %) and enables
64tracing of more components (--trace-config read,write,ssl).
66A fourth time adds tracing of all network components. (--trace-config network).
68Any addition of the verbose option after that has no effect.
70If you think this option does not give you the right details, consider using
71--trace or --trace-ascii instead. Or use it only once and use --trace-config
72to trace the specific components you wish to see.
74Note that verbose output of curl activities and network traffic might contain
75sensitive data, including usernames, credentials or secret data content. Be
76aware and be careful when sharing trace logs with others.
78When the output contains protocol headers, those lines might include carriage
79return (ASCII code 13) characters, even on platforms that otherwise normally
80only use linefeed to signify line separations - as curl shows the exact
81contents arriving from the server.
Diagnostics4 git calls · 28 ms
CallStatusSizeTime028 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 · 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.2 KiB · hit24 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=24
git.response.bytes=1259
git.response.cache=HIT
git.response.duration_ms=24
git.fetch.wants=b5d6b57d64b6e20bc3ff7f8d2a2c0e0b09825421
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=1259
git.pkt.payload.max=1238
git.sideband.band1.bytes=1237
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
a5e325f06e7998f1
Request
4153d5c4…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format