From 4d04a25b6c3054499f7fcbe774f0af39feb30654 Mon Sep 17 00:00:00 2001 From: Holger Levsen Date: Sat, 8 Dec 2012 16:50:11 +0100 Subject: REMOTE_HOST seems to be tricky, so 'properly' work around it... --- etc/apache2/sites-available/jenkins.debian.net | 2 ++ 1 file changed, 2 insertions(+) (limited to 'etc/apache2') diff --git a/etc/apache2/sites-available/jenkins.debian.net b/etc/apache2/sites-available/jenkins.debian.net index ddd739ee..0a6f3d09 100644 --- a/etc/apache2/sites-available/jenkins.debian.net +++ b/etc/apache2/sites-available/jenkins.debian.net @@ -24,7 +24,9 @@ # allow certain params only from alioth (token is used to trigger builds) RewriteEngine on RewriteCond %{REMOTE_ADDR} !217\.196\.43\.140 + # git.d.o is really vasks.d.o, so just allowing this trigger from any debian host should be fine. Anyone can run curl on alioth anyway #RewriteCond %{REMOTE_HOST} !.*.debian.org + # FIXME: REMOTE_HOST surely must work somehow? Also see etc/cron.daily/jenkins RewriteCond %{QUERY_STRING} token RewriteRule ^ - [F] -- cgit v1.2.3-70-g09d2