summaryrefslogtreecommitdiff
path: root/config/gitlab.yml.example
diff options
context:
space:
mode:
authorJacob Vosmaer <contact@jacobvosmaer.nl>2015-01-06 16:56:56 +0100
committerJacob Vosmaer <contact@jacobvosmaer.nl>2015-01-06 16:56:56 +0100
commitaf56c1dd323ee418eb8dbfa9eb35c7ec9ac58a66 (patch)
treeb3ab3629579ac4db3441c60cb48cc0c652dd73e7 /config/gitlab.yml.example
parentc8b2def2be44771ffb479ad989acc7eccf4012f8 (diff)
downloadgitlab-ce-af56c1dd323ee418eb8dbfa9eb35c7ec9ac58a66.tar.gz
White-list requests from 127.0.0.1
On some misconfigured GitLab servers, if you look in production.log it looks like all requests come from 127.0.0.1. To avoid unwanted banning we white-list 127.0.0.1 with this commit.
Diffstat (limited to 'config/gitlab.yml.example')
-rw-r--r--config/gitlab.yml.example3
1 files changed, 3 insertions, 0 deletions
diff --git a/config/gitlab.yml.example b/config/gitlab.yml.example
index b474063505f..5d801b9ae5b 100644
--- a/config/gitlab.yml.example
+++ b/config/gitlab.yml.example
@@ -300,6 +300,9 @@ production: &base
rack_attack:
git_basic_auth:
+ # Whitelist requests from 127.0.0.1 for web proxies (NGINX/Apache) with incorrect headers
+ # ip_whitelist: ["127.0.0.1"]
+ #
# Limit the number of Git HTTP authentication attempts per IP
# maxretry: 10
#