From 164f1c837fc778872b1d2f57c7e276e7caa8077e Mon Sep 17 00:00:00 2001 From: paultibbetts Date: Wed, 25 Jun 2025 14:17:33 +0000 Subject: [PATCH] Update URL for Caddy reverse proxy HTTPS guide (#236) Reviewed-on: https://gitea.com/gitea/docs/pulls/236 Reviewed-by: Lunny Xiao Co-authored-by: paultibbetts Co-committed-by: paultibbetts --- versioned_docs/version-1.24/administration/https-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-1.24/administration/https-support.md b/versioned_docs/version-1.24/administration/https-support.md index e8a95cb..c5ab2a4 100644 --- a/versioned_docs/version-1.24/administration/https-support.md +++ b/versioned_docs/version-1.24/administration/https-support.md @@ -86,7 +86,7 @@ After that, enable HTTPS by following one of these guides: - [nginx](https://nginx.org/en/docs/http/configuring_https_servers.html) - [apache2/httpd](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html) -- [caddy](https://caddyserver.com/docs/tls) +- [caddy](https://caddyserver.com/docs/automatic-https) :::note Enabling HTTPS only at the proxy level is referred as [TLS Termination Proxy](https://en.wikipedia.org/wiki/TLS_termination_proxy). The proxy server accepts incoming TLS connections, decrypts the contents, and passes the now unencrypted contents to Gitea. This is normally fine as long as both the proxy and Gitea instances are either on the same machine, or on different machines within private network (with the proxy is exposed to outside network). If your Gitea instance is separated from your proxy over a public network, or if you want full end-to-end encryption, you can also [enable HTTPS support directly in Gitea using built-in server](#using-the-built-in-server) and forward the connections over HTTPS instead.