docs: X-Forwarded-Proto: https
Additional documentation for running subdomain gateway behind reverse proxy with TLS.
Marcin Rataj committed
May 12, 2020 at 13:00 UTC
c5b30545bf9240ddeb5faad50ae626a09e6893f1
1 file changed
+4
-2
docs/config.md
+4
-2
@@ -614,8 +614,10 @@ Below is a list of the most common public gateway setups.
614
}
615
}'
616
```
617
- **Note:** this enables automatic redirects from content paths to subdomains
618
- `http://dweb.link/ipfs/{cid}` → `http://{cid}.ipfs.dweb.link`
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";`):
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)
623
```console