Artifactspublic-v0

curl

master
ply4 git calls26 ms288 KiB3 cachedprotocol v2
40 lines1.4 KiBRaw

--ipfs-gateway

Specify which gateway to use for IPFS and IPNS URLs. Not specifying this instead makes curl check if the IPFS_GATEWAY environment variable is set, or if a ~/.ipfs/gateway file holding the gateway URL exists.

If you run a local IPFS node, this gateway is by default available under http://localhost:8080. A full example URL would look like:

curl --ipfs-gateway http://localhost:8080 \
   ipfs://bafybeigagd5nmnn2iys2f3

There are many public IPFS gateways. See for example: https://ipfs.github.io/public-gateway-checker/

If you opt to go for a remote gateway you need to be aware that you completely trust the gateway. This might be fine in local gateways that you host yourself. With remote gateways there could potentially be malicious actors returning you data that does not match the request you made, inspect or even interfere with the request. You may not notice this when using curl. A mitigation could be to go for a "trustless" gateway. This means you locally verify the data. Consult the docs page on trusted vs trustless: https://docs.ipfs.tech/reference/http/gateway/#trusted-vs-trustless

1---
2c: Copyright (C) Mark Gaiser, <markg85@gmail.com>
3SPDX-License-Identifier: curl
4Long: ipfs-gateway
5Arg: <URL>
6Help: Gateway for IPFS
7Protocols: IPFS
8Added: 8.4.0
9Category: curl
10Multi: single
11See-also:
12 - help
13 - manual
14Example:
15 - --ipfs-gateway $URL ipfs://
16---
18# `--ipfs-gateway`
20Specify which gateway to use for IPFS and IPNS URLs. Not specifying this
21instead makes curl check if the IPFS_GATEWAY environment variable is set, or
22if a `~/.ipfs/gateway` file holding the gateway URL exists.
24If you run a local IPFS node, this gateway is by default available under
25`http://localhost:8080`. A full example URL would look like:
27 curl --ipfs-gateway http://localhost:8080 \
28 ipfs://bafybeigagd5nmnn2iys2f3
30There are many public IPFS gateways. See for example:
31https://ipfs.github.io/public-gateway-checker/
33If you opt to go for a remote gateway you need to be aware that you completely
34trust the gateway. This might be fine in local gateways that you host
35yourself. With remote gateways there could potentially be malicious actors
36returning you data that does not match the request you made, inspect or even
37interfere with the request. You may not notice this when using curl. A
38mitigation could be to go for a "trustless" gateway. This means you locally
39verify the data. Consult the docs page on trusted vs trustless:
40https://docs.ipfs.tech/reference/http/gateway/#trusted-vs-trustless
Diagnostics4 git calls · 26 ms
CallStatusSizeTime026 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=3
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 · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=21
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=3
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
fetch200840 B · hit21 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=840
git.response.cache=HIT
git.response.duration_ms=21
git.fetch.wants=16e197fcfefb2ebe434e7455e34883e72b7447df
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=840
git.pkt.payload.max=819
git.sideband.band1.bytes=818
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
a5e35e62f99f5cd4
Request
878921c8…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format