01d9b8bc7c
- convert ensure_trailing into ensure_trailing_slash - strdup the URL string to own it proper - use shorter variable names - combine some expressions - simplify error handling in ipfs_gateway() - add MAX_GATEWAY_URL_LEN + proper bailout if maximum is reached - ipfs-gateway.d polish and simplification - shorten ipfs error message + make them "synthetic" Closes #12281
33 lines
1.4 KiB
Makefile
33 lines
1.4 KiB
Makefile
c: Copyright (C) 2023, Mark Gaiser, <markg85@gmail.com>
|
|
SPDX-License-Identifier: curl
|
|
Long: ipfs-gateway
|
|
Arg: <URL>
|
|
Help: Gateway for IPFS
|
|
Added: 8.4.0
|
|
See-also: help manual
|
|
Category: ipfs
|
|
Example: --ipfs-gateway $URL ipfs://
|
|
Multi: single
|
|
---
|
|
Specify which gateway to use for IPFS and IPNS URLs. Not specifying this will
|
|
instead make 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://bafybeigagd5nmnn2iys2f3doro7ydrevyr2mzarwidgadawmamiteydbzi
|
|
|
|
There are many public IPFS gateways. See for example:
|
|
|
|
https://ipfs.github.io/public-gateway-checker/
|
|
|
|
WARNING: If you opt to go for a remote gateway you should be aware that you
|
|
completely trust the gateway. This is fine in local gateways as you host it
|
|
yourself. With remote gateways there could potentially be a malicious actor
|
|
returning you data that does not match the request you made, inspect or even
|
|
interfere with the request. You will not notice this when using curl. A
|
|
mitigation could be to go for a "trustless" gateway. This means you locally
|
|
verify that the data. Consult the docs page on trusted vs trustless:
|
|
https://docs.ipfs.tech/reference/http/gateway/#trusted-vs-trustless
|