Re: varnish with apache mod_auth

2017-03-18 Thread Hernán Marsili
> to that, any subsequent request will not be seen by either apache or > mod_auth at all. > > You have a few options: > 1) IP Whitelists are a rather poor means of authentication. Moving to > something else might be prudent. But that's not easy. > 2) There are probably VMOD

Re: varnish with apache mod_auth

2017-03-18 Thread Andrei
will return the cached response to any IP address that comes >>> calling. Even if the first request comes from a valid IP, which gets >>> passed through via X-Forward or similar, and mod_auth is tweaked to respond >>> to that, any subsequent request will not be seen by ei

Re: varnish with apache mod_auth

2017-03-17 Thread Guillaume Quintard
d_auth at all. >> >> You have a few options: >> 1) IP Whitelists are a rather poor means of authentication. Moving to >> something else might be prudent. But that's not easy. >> 2) There are probably VMODs that do something similar. If not and if the >> list of

Re: varnish with apache mod_auth

2017-03-17 Thread Hernán Marsili
ou could limit the IPs in VCL rather than > mod_auth. > 3) Push the list of IP addresses that can connect to the external port > down to IPTables or similar. > 4) Push the list of IP addresses to external Firewall, or Security Group > or whatever. > > > > On Thu, Mar

Re: varnish with apache mod_auth

2017-03-17 Thread Andrei
t; 1) IP Whitelists are a rather poor means of authentication. Moving to >>> something else might be prudent. But that's not easy. >>> 2) There are probably VMODs that do something similar. If not and if >>> the list of IPs isn't too long, you could limit the IPs in VC

Re: varnish with apache mod_auth

2017-03-17 Thread Guillaume Quintard
something similar. If not and if the >> list of IPs isn't too long, you could limit the IPs in VCL rather than >> mod_auth. >> 3) Push the list of IP addresses that can connect to the external port >> down to IPTables or similar. >> 4) Push the list of IP addresses to extern

Re: varnish with apache mod_auth

2017-03-17 Thread Hernán Marsili
nal port > down to IPTables or similar. > 4) Push the list of IP addresses to external Firewall, or Security Group > or whatever. > > > > On Thu, Mar 16, 2017 at 5:46 PM, Hernán Marsili <her...@cmsmedios.com> > wrote: > > Hi, > > We are having an issue with VARN

Re: varnish with apache mod_auth

2017-03-17 Thread Andrei
2017 at 5:46 PM, Hernán Marsili <her...@cmsmedios.com> > wrote: > >> Hi, >> >> We are having an issue with VARNISH and apache mod_auth. Varnish is on >> port 80 serving users and Apache is the backend. >> >> We have servers restricting access o

Re: varnish with apache mod_auth

2017-03-16 Thread Jason Price
<her...@cmsmedios.com> wrote: > Hi, > > We are having an issue with VARNISH and apache mod_auth. Varnish is on > port 80 serving users and Apache is the backend. > > We have servers restricting access only to authenticated users or certain > IP addresses. Since we

varnish with apache mod_auth

2017-03-16 Thread Hernán Marsili
Hi, We are having an issue with VARNISH and apache mod_auth. Varnish is on port 80 serving users and Apache is the backend. We have servers restricting access only to authenticated users or certain IP addresses. Since we installed Varnish the issue is that we need to enable 127.0.0.1