diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-11 21:10:14 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-11 21:10:14 +0000 |
| commit | 3ecbefc5818c1ca6b4ce54ac8afa148eac7bfdb2 (patch) | |
| tree | 6b0a8fee9d1a44df826df78e013154a35c331945 /doc/user/admin_area/reporting | |
| parent | 6e7be08ca5d6fac981284e7b1383b320a03d3a5d (diff) | |
| download | gitlab-ce-3ecbefc5818c1ca6b4ce54ac8afa148eac7bfdb2.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/admin_area/reporting')
| -rw-r--r-- | doc/user/admin_area/reporting/spamcheck.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/admin_area/reporting/spamcheck.md b/doc/user/admin_area/reporting/spamcheck.md index 0405d8a1ad7..5c305eff4fa 100644 --- a/doc/user/admin_area/reporting/spamcheck.md +++ b/doc/user/admin_area/reporting/spamcheck.md @@ -61,7 +61,7 @@ token as the API key. ## Running Spamcheck over TLS -Spamcheck service on its own can not communicate directly over TLS with GitLab. +Spamcheck service on its own cannot communicate directly over TLS with GitLab. However, Spamcheck can be deployed behind a reverse proxy which performs TLS termination. In such a scenario, GitLab can be made to communicate with Spamcheck over TLS by specifying `tls://` scheme for the external Spamcheck URL |