Allow direct varnish access for internal hosts
This allows internal that are in the purge acl to issue purge requests. Apache won't forward purge, since it doesn't know what that is.
This commit is contained in:
parent
4e08b900f4
commit
ec23aaf08a
2 changed files with 10 additions and 2 deletions
|
@ -34,10 +34,14 @@ custom_rules: [
|
|||
'-A INPUT -p tcp -m tcp -s 192.168.1.59 --dport 873 -j ACCEPT',
|
||||
'-A INPUT -p tcp -m tcp -s 209.132.181.102 --dport 873 -j ACCEPT',
|
||||
|
||||
# only allow varnish from localhost
|
||||
# allow varnish from localhost
|
||||
'-A INPUT -p tcp -m tcp -s 127.0.0.1 --dport 6081 -j ACCEPT',
|
||||
'-A INPUT -p tcp -m tcp -s 127.0.0.1 --dport 6082 -j ACCEPT',
|
||||
|
||||
# also allow varnish from internal for purge requests
|
||||
'-A INPUT -p tcp -m tcp -s 192.168.1.0/24 --dport 6081 -j ACCEPT',
|
||||
'-A INPUT -p tcp -m tcp -s 10.5.126.0/24 --dport 6081 -j ACCEPT',
|
||||
|
||||
# Allow koschei.cloud to talk to the inbound fedmsg relay.
|
||||
'-A INPUT -p tcp -m tcp --dport 9941 -s 209.132.184.151 -j ACCEPT',
|
||||
# Allow jenkins.cloud to talk to the inbound fedmsg relay.
|
||||
|
|
|
@ -33,10 +33,14 @@ custom_rules: [
|
|||
'-A INPUT -p tcp -m tcp -s 10.5.126.13 --dport 873 -j ACCEPT',
|
||||
'-A INPUT -p tcp -m tcp -s 192.168.1.59 --dport 873 -j ACCEPT',
|
||||
|
||||
# only allow varnish from localhost
|
||||
# allow varnish from localhost
|
||||
'-A INPUT -p tcp -m tcp -s 127.0.0.1 --dport 6081 -j ACCEPT',
|
||||
'-A INPUT -p tcp -m tcp -s 127.0.0.1 --dport 6082 -j ACCEPT',
|
||||
|
||||
# also allow varnish from internal for purge requests
|
||||
'-A INPUT -p tcp -m tcp -s 192.168.1.0/24 --dport 6081 -j ACCEPT',
|
||||
'-A INPUT -p tcp -m tcp -s 10.5.126.0/24 --dport 6081 -j ACCEPT',
|
||||
|
||||
# Allow koschei.cloud to talk to the inbound fedmsg relay.
|
||||
'-A INPUT -p tcp -m tcp --dport 9941 -s 209.132.184.151 -j ACCEPT',
|
||||
# Allow jenkins.cloud to talk to the inbound fedmsg relay.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue