Option cleanups: --get is not upload --form* are post - added several options into ldap, smtp, imap and pop3 - shortened the category descriptions in the list category curl fixes: --create-dirs removed from 'curl' --ftp-create-dirs removed from 'curl' --netrc moved to 'auth' from 'curl' --netrc-file moved to 'auth' from 'curl' --netrc-optional moved to 'auth' from 'curl' --no-buffer moved to 'output' from 'curl' --no-clobber removed from 'curl' --output removed from 'curl' --output-dir removed from 'curl' --remove-on-error removed from 'curl' Add a "global" category: - Made all "global" options set this category Add a "deprecated" category: - Moved the deprecated options to it (maybe they should not be in any category long term) Add a 'timeout' category - Put a number of appropriate options in it Add an 'ldap' category - Put the LDAP related option in there Remove categories "ECH" and "ipfs" - They should not be categories. Had only one single option each. Remove category "misc" - It should not be a category as it is impossible to know when to browse it. --use-ascii moved to ftp and output --xattr moved to output --service-name moved to auth Managen fixes: - errors if an option is given a category name that is not already setup for in code - verifies that options set `scope: global` also is put in category `global´ Closes #14101
40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
---
|
|
c: Copyright (C) Mark Gaiser, <markg85@gmail.com>
|
|
SPDX-License-Identifier: curl
|
|
Long: ipfs-gateway
|
|
Arg: <URL>
|
|
Help: Gateway for IPFS
|
|
Protocols: IPFS
|
|
Added: 8.4.0
|
|
Category: curl
|
|
Multi: single
|
|
See-also:
|
|
- help
|
|
- manual
|
|
Example:
|
|
- --ipfs-gateway $URL ipfs://
|
|
---
|
|
|
|
# `--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://bafybeigagd5nmnn2iys2f3doro7ydrevyr2mzarwidgadawmamiteydbzi
|
|
|
|
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 that the data. Consult the docs page on trusted vs trustless:
|
|
https://docs.ipfs.tech/reference/http/gateway/#trusted-vs-trustless
|