From 5bf5782f9898ac301dbc5f5330f0f3454794bb9c Mon Sep 17 00:00:00 2001 From: Florian Scholdei Date: Wed, 24 Jul 2024 11:17:39 +0200 Subject: [PATCH] Fix broken link in docs --- docs/en/administration/reverse-proxies.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/administration/reverse-proxies.md b/docs/en/administration/reverse-proxies.md index b093b58337..18b5e5b150 100644 --- a/docs/en/administration/reverse-proxies.md +++ b/docs/en/administration/reverse-proxies.md @@ -8,14 +8,14 @@ SCM-Manager can run behind any reverse proxy, but a few rules must be respected. The reverse proxy should not encode slashes and the `X-Forwarded-For` and `X-Forwarded-Host` headers must be sent to SCM-Manager. If the proxy uses a different protocol as the SCM-Manager e.g. https on proxy and http on scm-manager, the -`X-Forwarded-Proto` header must be send too. +`X-Forwarded-Proto` header must be sent too. If `XSRF protection` is enabled on the SCM-Manager server, the cookie has to be `HttpOnly=false` and must not be modified. For SCM-Manager to work properly, the configuration `forwardHeadersEnabled` has to be set to `true` in the `config.yml`. To avoid timeouts due to caching in the reverse proxies, you also might want to increase the `idleTimeout` to a higher value, depending on the size of your repositories (you might want to start with `300000`, that would be five minutes). -See the section about reverse proxies in [SCM-Server onfiguration](scm-server.md) for more information. +See the section about reverse proxies in [SCM-Server configuration](../scm-server/) for more information. ## nginx