Updated Warpgate behind a reverse proxy (markdown)

Eugene 2024-08-24 23:26:02 +02:00
parent ea7e33e4ab
commit a8dfb6ac86

@ -1,7 +1,7 @@
Warpgate doesn't need any specific configuration except in the following case:
* When using **single sign-on**, make sure your reverse proxy supplies the correct `Host` and `X-Forwarded-Proto` headers - this allows Warpgate to construct correct redirect URLs.
* Set `http.trust_x_forwarded_for` to `true` in the config file.
* Set `http.trust_x_forwarded_headers` to `true` in the config file.
Example for NGINX: