forks/forgejo
1
0
Fork 0
Code Releases Activity

[doc] https-setup: explain relative paths for {CERT,KEY}_FILE fields. (#18244)

Browse source 
Closes: https://github.com/go-gitea/gitea/issues/14401
This commit is contained in:
M. Zhou 2022-01-11 23:18:28 -05:00 committed by GitHub
parent ee8718e452
commit ba9e4e2570
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/content/doc/usage/https-support.md
View file

@ -40,6 +40,8 @@ KEY_FILE = key.pem
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.
To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server-server).
For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well.
### Setting up HTTP redirection
The Gitea server is only able to listen to one port; to redirect HTTP requests to the HTTPS port, you will need to enable the HTTP redirection service: