[Docs] Clarify TLS Termination Proxy #4485

New Issue

GiteaMirror · 2025-11-02T05:52:24-06:00

GiteaMirror commented

2025-11-02 05:52:24 -06:00

Originally created by @bagasme on GitHub (Dec 14, 2019).

Description

On HTTPS Setup, reverse proxy can be used for providing HTTPS instance. In reality, such setup is called TLS Termination Proxy.

Perhaps the docs can be rewritten as:

You can also enable HTTPS by using reverse proxy. Set up your favorite reverse proxy (Apache,
NGINX, or Caddy) and follow documentation of the program of your choice to enable HTTPS site.

NOTE: Enabling HTTPS by this method is referred as TLS Termination Proxy. The reverse proxy
handle TLS connections, and decrypted them for passing to Gitea. This is fine as long as the reverse
proxy and Gitea instance are either on the same machine, or on different machine on private
network (the proxy is exposed to outside network). If your Gitea instance is on public network, and
you want to enable HTTPS with reverse proxy, it is recommended to also encrypt connections from
your proxy to Gitea by follow instructions for built-in server and change proxy URL to https://[URL].

Originally created by @bagasme on GitHub (Dec 14, 2019).   # Description On [HTTPS Setup](https://docs.gitea.io/en-us/https-setup/), reverse proxy can be used for providing HTTPS instance. In reality, such setup is called [TLS Termination Proxy](https://en.wikipedia.org/wiki/TLS_termination_proxy). Perhaps the docs can be rewritten as: ``` You can also enable HTTPS by using reverse proxy. Set up your favorite reverse proxy (Apache, NGINX, or Caddy) and follow documentation of the program of your choice to enable HTTPS site. NOTE: Enabling HTTPS by this method is referred as TLS Termination Proxy. The reverse proxy handle TLS connections, and decrypted them for passing to Gitea. This is fine as long as the reverse proxy and Gitea instance are either on the same machine, or on different machine on private network (the proxy is exposed to outside network). If your Gitea instance is on public network, and you want to enable HTTPS with reverse proxy, it is recommended to also encrypt connections from your proxy to Gitea by follow instructions for built-in server and change proxy URL to https://[URL]. ```

GiteaMirror added the type/docs label 2025-11-02 05:52:24 -06:00

GiteaMirror closed this issue

2025-11-02 05:52:25 -06:00

GiteaMirror commented

2025-11-02 05:52:25 -06:00

@lunny commented on GitHub (Dec 14, 2019):

Please send a PR to update that.

@lunny commented on GitHub (Dec 14, 2019): Please send a PR to update that.

GiteaMirror commented

2025-11-02 05:52:25 -06:00

@bagasme commented on GitHub (Dec 15, 2019):

@lunny Sorry, I'm not trying to open a PR yet currently, just a suggestion.

Why? I only have metered internet connection (about 1 GB per day). Getting code.gitea.io sources via go get can easily exhaust internet quota quickly.

@bagasme commented on GitHub (Dec 15, 2019): @lunny Sorry, I'm not trying to open a PR yet currently, just a suggestion. Why? I only have metered internet connection (about 1 GB per day). Getting `code.gitea.io` sources via `go get` can easily exhaust internet quota quickly.

GiteaMirror commented

2025-11-02 05:52:25 -06:00

@bagasme commented on GitHub (Dec 25, 2019):

I had opened PR @ #9491.

@bagasme commented on GitHub (Dec 25, 2019): I had opened PR @ #9491.

GiteaMirror referenced this issue

2025-11-02 13:08:12 -06:00

[PR #4485] [MERGED] Prevent html entity escaping (#4471) #17394

GiteaMirror referenced this issue

2025-11-02 13:08:43 -06:00

[PR #4488] [MERGED] Add 1.5.0-rc2 changelog #17396

Sign in to join this conversation.