Artifactspublic-v0

curl

master
ply4 git calls42 ms288 KiB3 cachedprotocol v2
42 lines1.5 KiBRaw

--cookie-jar

Specify to which file you want curl to write all cookies after a completed operation. curl writes all cookies from its in-memory cookie storage to the given file at the end of operations. Even if no cookies are known, a file is created so that it removes any formerly existing cookies from the file. The file uses the Netscape cookie file format. If you set the filename to a single minus, "-", the cookies are written to stdout.

The file specified with --cookie-jar is only used for output. No cookies are read from the file. To read cookies, use the --cookie option. Both options can specify the same file.

This command line option activates the cookie engine that makes curl record and use cookies. The --cookie option also activates it.

If the cookie jar cannot be created or written to, the whole curl operation does not fail or even report an error clearly. Using --verbose gets a warning displayed, but that is the only visible feedback you get about this possibly lethal situation.

You may want to restrict your umask to prevent other users on the same system to access the created file.

1---
2c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
3SPDX-License-Identifier: curl
4Short: c
5Long: cookie-jar
6Arg: <filename>
7Protocols: HTTP
8Help: Save cookies to <filename> after operation
9Category: http
10Added: 7.9
11Multi: single
12See-also:
13 - cookie
14 - junk-session-cookies
15Example:
16 - -c store-here.txt $URL
17 - -c store-here.txt -b read-these $URL
18---
20# `--cookie-jar`
22Specify to which file you want curl to write all cookies after a completed
23operation. curl writes all cookies from its in-memory cookie storage to the
24given file at the end of operations. Even if no cookies are known, a file is
25created so that it removes any formerly existing cookies from the file. The
26file uses the Netscape cookie file format. If you set the filename to a single
27minus, "-", the cookies are written to stdout.
29The file specified with --cookie-jar is only used for output. No cookies are
30read from the file. To read cookies, use the --cookie option. Both options
31can specify the same file.
33This command line option activates the cookie engine that makes curl record
34and use cookies. The --cookie option also activates it.
36If the cookie jar cannot be created or written to, the whole curl operation
37does not fail or even report an error clearly. Using --verbose gets a warning
38displayed, but that is the only visible feedback you get about this possibly
39lethal situation.
41You may want to restrict your umask to prevent other users on the same system
42to access the created file.
Diagnostics4 git calls · 42 ms
CallStatusSizeTime042 ms
discover200152 B3 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 · hit4 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=35
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
fetch200834 B · hit35 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=834
git.response.cache=HIT
git.response.duration_ms=35
git.fetch.wants=de09fd5274d4910a277b5c229f090c03bccd56a5
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=834
git.pkt.payload.max=813
git.sideband.band1.bytes=812
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
a5e1c2f14add6c75
Request
3340915e…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format