From c11302233b023d802679e54bcb002ab582bdb0af Mon Sep 17 00:00:00 2001 From: bircni Date: Thu, 22 Oct 2026 21:35:34 +0200 Subject: [PATCH] docs: clarify reverse proxy authentication requirements (#39940) Document that reverse proxy authentication requires Gitea to be reachable only through the authenticating proxy, and which routes each setting covers. Docs: https://gitea.com/gitea/docs/pulls/604 Co-authored-by: silverwind --- custom/conf/app.example.ini | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/custom/conf/app.example.ini b/custom/conf/app.example.ini index 86b63b7875d..6df6840848a 100644 --- a/custom/conf/app.example.ini +++ b/custom/conf/app.example.ini @@ -865,9 +865,10 @@ LEVEL = Info ;; Allow users to sign-in with a passkey ;ENABLE_PASSKEY_AUTHENTICATION = true ;; -;; More detail: https://github.com/gogits/gogs/issues/165 +;; Reverse proxy authentication for the web interface, Git over HTTP, Git LFS and the package registry. +;; Gitea must only be reachable through the proxy, which must set or remove the authentication headers on every request. ;ENABLE_REVERSE_PROXY_AUTHENTICATION = false -; Enable this to allow reverse proxy authentication for API requests, the reverse proxy is responsible for ensuring that no CSRF is possible. +;; Reverse proxy authentication for the REST API under /api/v1. ;ENABLE_REVERSE_PROXY_AUTHENTICATION_API = false ;ENABLE_REVERSE_PROXY_AUTO_REGISTRATION = false ;ENABLE_REVERSE_PROXY_EMAIL = false