Michel Santos
2007-08-30 09:02:53 UTC
There is appearently an acl bug
acls do not work for peers
#
acl all src 200.152.80.0/20
acl danger urlpath_regex -i instal\.html
http_access deny all danger
#
so far this works for "all", I mean it blocks as wanted
#
acl all src 200.152.80.0/20
acl peer src 200.152.83.40
acl danger urlpath_regex -i instal\.html
http_access deny all danger
http_access deny peer danger
#
does NOT when accessing directly from a browser from 200.152.83.40
and does NOT work when configuring localhost as proxy on 200.152.83.40
does only block when I configure the acl on 200.152.83.40's squid
same for dstdomain and other acl attributes
that is not a feature but a bug am I right?
michel
...
****************************************************
Datacenter Matik http://datacenter.matik.com.br
E-Mail e Data Hosting Service para Profissionais.
****************************************************
acls do not work for peers
#
acl all src 200.152.80.0/20
acl danger urlpath_regex -i instal\.html
http_access deny all danger
#
so far this works for "all", I mean it blocks as wanted
#
acl all src 200.152.80.0/20
acl peer src 200.152.83.40
acl danger urlpath_regex -i instal\.html
http_access deny all danger
http_access deny peer danger
#
does NOT when accessing directly from a browser from 200.152.83.40
and does NOT work when configuring localhost as proxy on 200.152.83.40
does only block when I configure the acl on 200.152.83.40's squid
same for dstdomain and other acl attributes
that is not a feature but a bug am I right?
michel
...
****************************************************
Datacenter Matik http://datacenter.matik.com.br
E-Mail e Data Hosting Service para Profissionais.
****************************************************