Artifactspublic-v0

curl

master
ply4 git calls189 ms288 KiB2 cachedprotocol v2
64 lines2.6 KiBRaw

--cookie

This option has two slightly separate cookie sending functions.

Either: pass the exact data to send to the HTTP server in the Cookie header. It is supposedly data previously received from the server in a Set-Cookie: line. The data should be in the format NAME1=VALUE1; NAME2=VALUE2. When given a set of specific cookies, curl populates its cookie header with this content explicitly in all outgoing request(s). If multiple requests are done due to authentication, followed redirects or similar, they all get this cookie header passed on.

Or: If no = symbol is used in the argument, it is instead treated as a filename to read previously stored cookie from. This option also activates the cookie engine which makes curl record incoming cookies, which may be handy if you are using this in combination with the --location option or do multiple URL transfers on the same invoke.

If the filename is a single minus ("-"), curl reads the contents from stdin. If the filename is an empty string ("") and is the only cookie input, curl activates the cookie engine without any cookies.

The file format of the file to read cookies from should be plain HTTP headers (Set-Cookie style) or the Netscape/Mozilla cookie file format. We discourage the use of the HTTP header style.

The file specified with --cookie is only used as input. No cookies are written to that file. To store cookies, use the --cookie-jar option.

If you read cookies from a plain HTTP headers file, make sure each Set-Cookie line specifies a Domain attribute. Without an explicit domain, the cookie cannot be reliably matched to a target host and may be applied in unexpected ways. We suggest using the Netscape file format instead.

Users often want to both read cookies from a file and write updated cookies back to a file, so using both --cookie and --cookie-jar in the same command line is common. curl ignores filenames specified with --cookie which do not exist or point to a directory.

If curl is built with PSL (Public Suffix List) support, it detects and discards cookies that are specified for such suffix domains that should not be allowed to have cookies. If curl is not built with PSL support, it has no ability to stop super cookies.

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Short: b
5Long: cookie
6Arg: <data|filename>
7Protocols: HTTP
8Help: Send cookies from string/load from file
9Category: http
10Added: 4.9
11Multi: append
12See-also:
13 - cookie-jar
14 - junk-session-cookies
15Example:
16 - -b "" $URL
17 - -b cookiefile $URL
18 - -b cookiefile -c cookiefile $URL
19 - -b name=Jane $URL
20---
22# `--cookie`
24This option has two slightly separate cookie sending functions.
26Either: pass the exact data to send to the HTTP server in the Cookie header.
27It is supposedly data previously received from the server in a `Set-Cookie:`
28line. The data should be in the format `NAME1=VALUE1; NAME2=VALUE2`. When
29given a set of specific cookies, curl populates its cookie header with this
30content explicitly in all outgoing request(s). If multiple requests are done
31due to authentication, followed redirects or similar, they all get this cookie
32header passed on.
34Or: If no `=` symbol is used in the argument, it is instead treated as a
35filename to read previously stored cookie from. This option also activates the
36cookie engine which makes curl record incoming cookies, which may be handy if
37you are using this in combination with the --location option or do multiple
38URL transfers on the same invoke.
40If the filename is a single minus ("-"), curl reads the contents from stdin.
41If the filename is an empty string ("") and is the only cookie input, curl
42activates the cookie engine without any cookies.
44The file format of the file to read cookies from should be plain HTTP headers
45(Set-Cookie style) or the Netscape/Mozilla cookie file format. We discourage
46the use of the HTTP header style.
48The file specified with --cookie is only used as input. No cookies are written
49to that file. To store cookies, use the --cookie-jar option.
51If you read cookies from a plain HTTP headers file, make sure each
52`Set-Cookie` line specifies a `Domain` attribute. Without an explicit domain,
53the cookie cannot be reliably matched to a target host and may be applied in
54unexpected ways. We suggest using the Netscape file format instead.
56Users often want to both read cookies from a file and write updated cookies
57back to a file, so using both --cookie and --cookie-jar in the same command
58line is common. curl ignores filenames specified with --cookie which do not
59exist or point to a directory.
61If curl is built with PSL (**Public Suffix List**) support, it detects and
62discards cookies that are specified for such suffix domains that should not be
63allowed to have cookies. If curl is *not* built with PSL support, it has no
64ability to stop super cookies.
Diagnostics4 git calls · 189 ms
CallStatusSizeTime0189 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 KiB183 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=183
git.response.bytes=1356
git.response.cache=MISS
git.response.duration_ms=183
git.fetch.wants=95b0a8c3c81f244dce9a2435f19c62b8f0eaef02
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=1356
git.pkt.payload.max=1335
git.sideband.band1.bytes=1334
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
a5e2ee24ba3f77be
Request
d5aa5de3…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format