History

Reformat docs (#13897)

Patrick Schratz committed 5 years ago

Commit af796771 parent 97ab82086 files · +1128 −970Browse files

Showing the changes to docs/content/doc/usage/https-support.md (1 of 86 files). Show all

Unified · Split

docs/content/doc/usage/https-support.md+10−5
@@ -3,7 +3,7 @@ date: "2018-06-02T11:00:00+02:00" · 2 unmodified lines
33 title: "Usage: HTTPS setup"
44 slug: "https-setup"
55 weight: 12
6−toc: true
6+toc: false
77 draft: false
88 menu:
99 sidebar:
@@ -15,6 +15,10 @@ menu: · 5 unmodified lines
1515
1616 # HTTPS setup to encrypt connections to Gitea
1717
18+**Table of Contents**
19+
20+{{< toc >}}
21+
1822 ## Using the built-in server
1923
2024 Before you enable HTTPS, make sure that you have valid SSL/TLS certificates.
@@ -32,6 +36,7 @@ HTTP_PORT = 3000 · 11 unmodified lines
3236 CERT_FILE = cert.pem
3337 KEY_FILE = key.pem
3438 ```
39+
3540 Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship.
3641 To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server).
3742
@@ -66,14 +71,14 @@ LETSENCRYPT_EMAIL=email@example.com · 28 unmodified lines
6671
6772 To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server).
6873
69−## Using reverse proxy
74+## Using a reverse proxy
7075
7176 Setup up your reverse proxy as shown in the [reverse proxy guide](../reverse-proxies).
7277
7378 After that, enable HTTPS by following one of these guides:
7479
75−* [nginx](https://nginx.org/en/docs/http/configuring_https_servers.html)
76−* [apache2/httpd](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html)
77−* [caddy](https://caddyserver.com/docs/tls)
80+- [nginx](https://nginx.org/en/docs/http/configuring_https_servers.html)
81+- [apache2/httpd](https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html)
82+- [caddy](https://caddyserver.com/docs/tls)
7883
7984 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.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t