chore: update X-Forwarded-Proto copy text
Co-authored-by: Steven Allen <steven@stebalien.com>
Marcin Rataj committed
May 13, 2020 at 15:07 UTC
10aaf243042b26d694b0fded27e7d823525782a7
1 file changed
+1
-1
docs/config.md
+1
-1
@@ -616,7 +616,7 @@ Below is a list of the most common public gateway setups.
616
```
617
**Note I:** this enables automatic redirects from content paths to subdomains:
618
`http://dweb.link/ipfs/{cid}` → `http://{cid}.ipfs.dweb.link`
619
- **Note II:** if you run go-ipfs behind reverse proxy that provides TLS make it add `X-Forwarded-Proto: https` HTTP header to ensure users are redirected to `https://` URLs (Nginx directive: `proxy_set_header X-Forwarded-Proto "https";`):
619
+ **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";`.:
620
`https://dweb.link/ipfs/{cid}` → `https://{cid}.ipfs.dweb.link`
621
622
* 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)