diff options
| author | Bagas Sanjaya <bagasdotme@gmail.com> | 2020-01-08 16:20:15 +0700 |
|---|---|---|
| committer | Antoine GIRARD <sapk@users.noreply.github.com> | 2020-01-08 10:20:15 +0100 |
| commit | 74d6ec6807f2191d259310a487458be377d91563 (patch) | |
| tree | b6d2724b5c871ae25a120a03ff70f5b8f70e1115 | |
| parent | e88d67b774ae615208b25133c299f2d50b3a018b (diff) | |
| download | gitea-74d6ec6807f2191d259310a487458be377d91563.tar.gz gitea-74d6ec6807f2191d259310a487458be377d91563.zip | |
[Docs] Grammar Edit on Enabling HTTPS Using Reverse Proxy (#9649)
* Use infinitives for accept and pass
* Close parentheeses for proxy exposed
| -rw-r--r-- | docs/content/doc/usage/https-support.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/content/doc/usage/https-support.md b/docs/content/doc/usage/https-support.md index a0afed7f80..a94372ff1f 100644 --- a/docs/content/doc/usage/https-support.md +++ b/docs/content/doc/usage/https-support.md @@ -76,4 +76,4 @@ After that, enable HTTPS by following one of these guides: * [apache2/httpd](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html) * [caddy](https://caddyserver.com/docs/tls) -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 accepted incoming TLS connections, decrypts the contents, and pass 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. +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. |