mirror of
https://gitea.com/gitea/docs.git
synced 2026-03-27 14:11:03 +07:00
Update docs/administration/reverse-proxies.md (#280)
Using a full certificate chain will prevent errors from using git directly on the URL to be pulled/cloned. (Error: 'fatal: unable to access 'https://git.example.net/git/sarah/test.git': server certificate verification failed. CAfile: none CRLfile: none') Reviewed-on: https://gitea.com/gitea/docs/pulls/280 Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: vincentkersten <vincentkersten@noreply.gitea.com> Co-committed-by: vincentkersten <vincentkersten@noreply.gitea.com>
This commit is contained in:
committed by
Lunny Xiao
parent
c586a396b8
commit
3578007c38
@@ -14,6 +14,7 @@ aliases:
|
||||
2. Make the reverse-proxy pass `https://git.example.com/foo` to `http://gitea:3000/foo`.
|
||||
3. Make sure the reverse-proxy does not decode the URI. The request `https://git.example.com/a%2Fb` should be passed as `http://gitea:3000/a%2Fb`.
|
||||
4. Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea to make Gitea see the real URL being visited.
|
||||
5. Make sure your webserver has a certificate, including all intermediate and RootCA certificates, for `git clone` and `git pull` to work.
|
||||
|
||||
### Use a sub-path
|
||||
|
||||
|
||||
Reference in New Issue
Block a user