From 580d68685c705293da2d162b466e6b3d94bfb8ba Mon Sep 17 00:00:00 2001 From: Marcin Rataj Date: Fri, 10 Jul 2020 19:40:44 +0200 Subject: [PATCH] docs: document X-Forwarded-Host --- docs/config.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/config.md b/docs/config.md index 2274bb569..9a1fe3754 100644 --- a/docs/config.md +++ b/docs/config.md @@ -698,8 +698,11 @@ Below is a list of the most common public gateway setups. ``` **Note I:** this enables automatic redirects from content paths to subdomains: `http://dweb.link/ipfs/{cid}` → `http://{cid}.ipfs.dweb.link` - **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";`.: - `https://dweb.link/ipfs/{cid}` → `https://{cid}.ipfs.dweb.link` + **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";`.: + `http://dweb.link/ipfs/{cid}` → `https://{cid}.ipfs.dweb.link` + **Note III:** we also support `X-Forwarded-Proto: example.com` if you want to override subdomain gateway host from the original request: + `http://dweb.link/ipfs/{cid}` → `http://{cid}.ipfs.example` + * Public [path gateway](https://docs.ipfs.io/how-to/address-ipfs-on-web/#path-gateway) at `http://ipfs.io/ipfs/{cid}` (no Origin separation) ```console