From 628f9da0de79703e5a107267c8f27bab5c40e000 Mon Sep 17 00:00:00 2001
From: 8ctopus <13252042+8ctopus@users.noreply.github.com>
Date: Thu, 10 Oct 2019 04:11:25 +0500
Subject: [PATCH] =?UTF-8?q?Doc=20recommend=20to=20use=20reverse=20proxy=20?=
 =?UTF-8?q?if=20Apache/nginx=20is=20also=20running=20on=E2=80=A6=20(#8384)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* Doc recommend to use reverse proxy if Apache/nginx is also running on server

* Update docs/content/doc/usage/https-support.md

Co-Authored-By: John Olheiser <42128690+jolheiser@users.noreply.github.com>
---
 docs/content/doc/usage/https-support.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/content/doc/usage/https-support.md b/docs/content/doc/usage/https-support.md
index 22cbc684a..e2b5332c0 100644
--- a/docs/content/doc/usage/https-support.md
+++ b/docs/content/doc/usage/https-support.md
@@ -20,6 +20,8 @@ menu:
 Before you enable HTTPS, make sure that you have valid SSL/TLS certificates.
 You could use self-generated certificates for evaluation and testing. Please run `gitea cert --host [HOST]` to generate a self signed certificate.
 
+If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide]({{< relref "doc/usage/reverse-proxies.en-us.md" >}}).
+
 To use Gitea's built-in HTTPS support, you must change your `app.ini` file:
 
 ```ini