Update docs-beta links to final URLs
Jessica Schilling committed
May 28, 2020 at 11:14 UTC
766023311a7084d56cc336f0a65add4a0457b8e6
1 file changed
+5
-5
docs/config.md
+5
-5
@@ -510,7 +510,7 @@ Default: `[]`
510
A boolean to configure whether the gateway at the hostname provides [Origin isolation](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy)
511
between content roots.
512
513
-- `true` - enables [subdomain gateway](#https://docs-beta.ipfs.io/how-to/address-ipfs-on-web/#subdomain-gateway) at `http://*.{hostname}/`
513
+- `true` - enables [subdomain gateway](#https://docs.ipfs.io/how-to/address-ipfs-on-web/#http-gateways) at `http://*.{hostname}/`
514
- **Requires whitelist:** make sure respective `Paths` are set.
515
For example, `Paths: ["/ipfs", "/ipns"]` are required for `http://{cid}.ipfs.{hostname}` and `http://{foo}.ipns.{hostname}` to work:
516
```json
@@ -526,7 +526,7 @@ between content roots.
526
- **Backward-compatible:** requests for content paths such as `http://{hostname}/ipfs/{cid}` produce redirect to `http://{cid}.ipfs.{hostname}`
527
- **API:** if `/api` is on the `Paths` whitelist, `http://{hostname}/api/{cmd}` produces redirect to `http://api.{hostname}/api/{cmd}`
528
529
-- `false` - enables [path gateway](https://docs-beta.ipfs.io/how-to/address-ipfs-on-web/#path-gateway) at `http://{hostname}/*`
529
+- `false` - enables [path gateway](https://docs.ipfs.io/how-to/address-ipfs-on-web/#path-gateway) at `http://{hostname}/*`
530
- Example:
531
```json
532
"Gateway": {
@@ -580,7 +580,7 @@ $ ipfs config --json Gateway.PublicGateways '{"localhost": null }'
580
581
Below is a list of the most common public gateway setups.
582
583
-* Public [subdomain gateway](https://docs-beta.ipfs.io/how-to/address-ipfs-on-web/#subdomain-gateway) at `http://{cid}.ipfs.dweb.link` (each content root gets its own Origin)
583
+* Public [subdomain gateway](https://docs.ipfs.io/how-to/address-ipfs-on-web/#subdomain-gateway) at `http://{cid}.ipfs.dweb.link` (each content root gets its own Origin)
584
```console
585
$ ipfs config --json Gateway.PublicGateways '{
586
"dweb.link": {
@@ -594,7 +594,7 @@ Below is a list of the most common public gateway setups.
594
**Note II:** if you run go-ipfs behind a reverse proxy that provides TLS, make it adds a `X-Forwarded-Proto: https` HTTP header to ensure users are redirected to `https://`, not `http://`. The NGINX directive is `proxy_set_header X-Forwarded-Proto "https";`.:
595
`https://dweb.link/ipfs/{cid}` → `https://{cid}.ipfs.dweb.link`
596
597
-* Public [path gateway](https://docs-beta.ipfs.io/how-to/address-ipfs-on-web/#path-gateway) at `http://ipfs.io/ipfs/{cid}` (no Origin separation)
597
+* Public [path gateway](https://docs.ipfs.io/how-to/address-ipfs-on-web/#path-gateway) at `http://ipfs.io/ipfs/{cid}` (no Origin separation)
598
```console
599
$ ipfs config --json Gateway.PublicGateways '{
600
"ipfs.io": {
@@ -610,7 +610,7 @@ Below is a list of the most common public gateway setups.
610
```
611
* Note that `NoDNSLink: false` is the default (it works out of the box unless set to `true` manually)
612
613
-* Hardened, site-specific [DNSLink gateway](https://docs-beta.ipfs.io/how-to/address-ipfs-on-web/#dnslink-gateway).
613
+* Hardened, site-specific [DNSLink gateway](https://docs.ipfs.io/how-to/address-ipfs-on-web/#dnslink-gateway).
614
Disable fetching of remote data (`NoFetch: true`)
615
and resolving DNSLink at unknown hostnames (`NoDNSLink: true`).
616
Then, enable DNSLink gateway only for the specific hostname (for which data