On 14.05.2012 10:35, Frantisek Hanzlik wrote:
Hi all squid gurus,
I'm testing Squid v3.2.0@Linux/i686 and still have some minor
uncertainties. These directives seems be obsolete (Squid wrote not
"Warning", but "Error":
2012/05/13 22:13:28| ERROR: Directive 'ftp_list_width' is obsolete.
2012/05/1
Hi all squid gurus,
I'm testing Squid v3.2.0@Linux/i686 and still have some minor
uncertainties. These directives seems be obsolete (Squid wrote not
"Warning", but "Error":
2012/05/13 22:13:28| ERROR: Directive 'ftp_list_width' is obsolete.
2012/05/13 22:13:28| ERROR: Directive 'ignore_expect_100'
On 14.05.2012 06:48, Eliezer Croitoru wrote:
as you can see in the acl documentation at:
http://www.squid-cache.org/Doc/config/acl/
it seems like what you need is myport that you mentioned.
there is no need what so ever for this to use two squid instances.
you should restrict the http_access to
as you can see in the acl documentation at:
http://www.squid-cache.org/Doc/config/acl/
it seems like what you need is myport that you mentioned.
there is no need what so ever for this to use two squid instances.
you should restrict the http_access to by more explicit such as:
http_port 192.168.0
Hello Squid gurus,
I want use Squid with WPAD (DHCP/DNS) proxy autoconfiguration for
win clients. Unfortunately there are some services (antivirus), which
does not recognizes/are not able automatically configure for proxy
and still are accessing HTTP sites directly at port 80. I imagine
configurat
