VladPolskiy/gitea-docs
1
0
Fork 0
mirror of https://gitea.com/gitea/docs.git synced 2025-07-24 09:59:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update URL for Caddy reverse proxy HTTPS guide (#236)

Browse Source 
Reviewed-on: https://gitea.com/gitea/docs/pulls/236
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: paultibbetts <paultibbetts@noreply.gitea.com>
Co-committed-by: paultibbetts <paultibbetts@noreply.gitea.com>
This commit is contained in:
paultibbetts
2025-06-25 14:17:33 +00:00
committed by techknowlogick
parent 870f30e886
commit 164f1c837f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
versioned_docs/version-1.24/administration/https-support.md
View File

@ -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.