docs(config): X-Forwarded-Host
This fixes a bug and documents X-Forwarded-Host License: MIT Signed-off-by: Marcin Rataj <lidel@lidel.org>
Marcin Rataj committed
Sep 4, 2020 at 18:51 UTC
76892f5c2f1acbf8af560e6b8e8aef47eb2770fb
1 file changed
+3
-3
docs/config.md
+3
-3
@@ -702,11 +702,11 @@ Below is a list of the most common public gateway setups.
702
}
703
}'
704
```
705
- **Note I:** this enables automatic redirects from content paths to subdomains:
705
+ **Backward-compatible:** this feature enables automatic redirects from content paths to subdomains:
706
`http://dweb.link/ipfs/{cid}` → `http://{cid}.ipfs.dweb.link`
707
- **Note II:** if you run go-ipfs behind a reverse proxy that provides TLS, make it add 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";`.:
707
+ **X-Forwarded-Proto:** if you run go-ipfs behind a reverse proxy that provides TLS, make it add 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";`.:
708
`http://dweb.link/ipfs/{cid}` → `https://{cid}.ipfs.dweb.link`
709
- **Note III:** we also support `X-Forwarded-Proto: example.com` if you want to override subdomain gateway host from the original request:
709
+ **X-Forwarded-Host:** we also support `X-Forwarded-Host: example.com` if you want to override subdomain gateway host from the original request:
710
`http://dweb.link/ipfs/{cid}` → `http://{cid}.ipfs.example.com`
711
712