romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-07-24 20:17:17 +03:00
Code Issues Projects Releases Packages Wiki Activity

badwords: re-sync with curl-www, fix issues found

Browse source 
Also:
- replace `manpage` with `man page`, add to `badwords.txt`.
- badwords.pl: import `-w` feature from curl-www, syncing the two
  scripts fully.
- badwords.txt: import missing items from curl-www, syncing the two
  files fully.
- pyspelling.words: drop `cURL` allowed word.

Closes #19468
This commit is contained in:
Viktor Szakats 2025-11-11 17:43:06 +01:00
parent ebc5fea64d
commit 4841e4290d
No known key found for this signature in database
GPG key ID: B5ABD165E2AEF201
27 changed files with 109 additions and 78 deletions
Download patch file Download diff file Expand all files Collapse all files

22
docs/IPFS.md
View file

@ -43,9 +43,9 @@ in this link:
`http://127.0.0.1:8080/ipfs/bafybeigagd5nmnn2iys2f3doro7ydrevyr2mzarwidgadawmamiteydbzi`
## cURL handling of the IPFS protocols
## curl handling of the IPFS protocols
The IPFS integration in cURL hides this gateway logic for you. Instead of
The IPFS integration in curl hides this gateway logic for you. Instead of
providing a full URL to a file on IPFS like this:
```
@ -57,7 +57,7 @@ You can provide it with the IPFS protocol instead:
curl ipfs://bafybeigagd5nmnn2iys2f3doro7ydrevyr2mzarwidgadawmamiteydbzi
```
With the IPFS protocol way of asking a file, cURL still needs to know the
With the IPFS protocol way of asking a file, curl still needs to know the
gateway. curl essentially just rewrites the IPFS based URL to a gateway URL.
### IPFS_GATEWAY environment variable
@ -67,7 +67,7 @@ gateway.
### Automatic gateway detection
When you provide no additional details to cURL then it:
When you provide no additional details to curl then it:
1. First looks for the `IPFS_GATEWAY` environment variable and use that if it
is set.
@ -75,12 +75,12 @@ When you provide no additional details to cURL then it:
means that you have a local gateway running and that file contains the URL
to your local gateway.
If cURL fails, you are presented with an error message and a link to this page
If curl fails, you are presented with an error message and a link to this page
to the option most applicable to solving the issue.
### `--ipfs-gateway` argument
You can also provide a `--ipfs-gateway` argument to cURL. This overrules any
You can also provide a `--ipfs-gateway` argument to curl. This overrules any
other gateway setting. curl does not fallback to the other options if the
provided gateway did not work.
@ -107,21 +107,21 @@ option follows the redirect.
## Error messages and hints
Depending on the arguments, cURL could present the user with an error.
Depending on the arguments, curl could present the user with an error.
### Gateway file and environment variable
cURL tried to look for the file: `~/.ipfs/gateway` but could not find it. It
curl tried to look for the file: `~/.ipfs/gateway` but could not find it. It
also tried to look for the `IPFS_GATEWAY` environment variable but could not
find that either. This happens when no extra arguments are passed to cURL and
find that either. This happens when no extra arguments are passed to curl and
letting it try to figure it out [automatically](#automatic-gateway-detection).
Any IPFS implementation that has gateway support should expose its URL in
`~/.ipfs/gateway`. If you are already running a gateway, make sure it exposes
the file where cURL expects to find it.
the file where curl expects to find it.
Alternatively you could set the `IPFS_GATEWAY` environment variable or pass
the `--ipfs-gateway` flag to the cURL command.
the `--ipfs-gateway` flag to the curl command.
### Malformed gateway URL