[squid-users] Re: Problem creating cache
I found my error. squid was looking into the wrong conf file. Markus Markus Moeller hua...@moeller.plus.com wrote in message news:k6v2q5$lmn$1...@ger.gmane.org... I try to create the cache with squid 3.2.2 but without success. How can I debug this ? -X does not give anything useful. # /opt/squid-3.2/sbin/squid -z -F 2012/11/01 23:56:09| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1' 2012/11/01 23:56:09| WARNING: because of this '127.0.0.1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '127.0.0.1' from the ACL named 'localhost' 2012/11/01 23:56:09| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1' 2012/11/01 23:56:09| WARNING: because of this '127.0.0.1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '127.0.0.1' from the ACL named 'localhost' 2012/11/01 23:56:09| WARNING: (B) '::1' is a subnetwork of (A) '::1' 2012/11/01 23:56:09| WARNING: because of this '::1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '::1' from the ACL named 'localhost' 2012/11/01 23:56:09| WARNING: (B) '::1' is a subnetwork of (A) '::1' 2012/11/01 23:56:09| WARNING: because of this '::1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '::1' from the ACL named 'localhost' 2012/11/01 23:56:09| WARNING: (B) '127.0.0.0/8' is a subnetwork of (A) '127.0.0.0/8' 2012/11/01 23:56:09| WARNING: because of this '127.0.0.0/8' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '127.0.0.0/8' from the ACL named 'to_localhost' 2012/11/01 23:56:09| WARNING: (B) '0.0.0.0' is a subnetwork of (A) '0.0.0.0' 2012/11/01 23:56:09| WARNING: because of this '0.0.0.0' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '0.0.0.0' from the ACL named 'to_localhost' 2012/11/01 23:56:09| WARNING: (B) '0.0.0.0' is a subnetwork of (A) '0.0.0.0' 2012/11/01 23:56:09| WARNING: because of this '0.0.0.0' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '0.0.0.0' from the ACL named 'to_localhost' 2012/11/01 23:56:09| WARNING: (B) '::1' is a subnetwork of (A) '::1' 2012/11/01 23:56:09| WARNING: because of this '::1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '::1' from the ACL named 'to_localhost' 2012/11/01 23:56:09| WARNING: (B) '::1' is a subnetwork of (A) '::1' 2012/11/01 23:56:09| WARNING: because of this '::1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09| WARNING: You should probably remove '::1' from the ACL named 'to_localhost' opensuse12:/etc/init.d # 2012/11/01 23:56:09 kid1| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1' 2012/11/01 23:56:09 kid1| WARNING: because of this '127.0.0.1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09 kid1| WARNING: You should probably remove '127.0.0.1' from the ACL named 'localhost' 2012/11/01 23:56:09 kid1| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1' 2012/11/01 23:56:09 kid1| WARNING: because of this '127.0.0.1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09 kid1| WARNING: You should probably remove '127.0.0.1' from the ACL named 'localhost' 2012/11/01 23:56:09 kid1| WARNING: (B) '::1' is a subnetwork of (A) '::1' 2012/11/01 23:56:09 kid1| WARNING: because of this '::1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09 kid1| WARNING: You should probably remove '::1' from the ACL named 'localhost' 2012/11/01 23:56:09 kid1| WARNING: (B) '::1' is a subnetwork of (A) '::1' 2012/11/01 23:56:09 kid1| WARNING: because of this '::1' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09 kid1| WARNING: You should probably remove '::1' from the ACL named 'localhost' 2012/11/01 23:56:09 kid1| WARNING: (B) '127.0.0.0/8' is a subnetwork of (A) '127.0.0.0/8' 2012/11/01 23:56:09 kid1| WARNING: because of this '127.0.0.0/8' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09 kid1| WARNING: You should probably remove '127.0.0.0/8' from the ACL named 'to_localhost' 2012/11/01 23:56:09 kid1| WARNING: (B) '0.0.0.0' is a subnetwork of (A) '0.0.0.0' 2012/11/01 23:56:09 kid1| WARNING: because of this '0.0.0.0' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09 kid1| WARNING: You should probably remove '0.0.0.0' from the ACL named 'to_localhost' 2012/11/01 23:56:09 kid1| WARNING: (B) '0.0.0.0' is a subnetwork of (A) '0.0.0.0' 2012/11/01 23:56:09 kid1| WARNING: because of this '0.0.0.0' is ignored to keep splay tree searching predictable 2012/11/01 23:56:09 kid1| WARNING: You should probably remove '0.0.0.0' from the
[squid-users] ACL for client_persistent_connections per User-Agent?
Hello everybody I found that while behind Squid/3.1.6 in tproxy mode, the Microsoft AutoUpdate on Mac cannot check for updates (times out). Setting client_persistent_connections off cures the problem. Would it be possible to tell squid to disable client_persistent_connections for a particular request, matching for example User-Agent header? Thanks for your hints Petr
Re: [squid-users] Re: HTTPS traffic in normal transparent proxy
On 11/2/2012 6:23 PM, Markus wrote: Ok. I only have internet access via a http/s proxy. In your case the proxy server generates a new https request directly to the SSL-webserver but in my case the request must be send via parent http/s proxy. I only enabled dns-requests for this one virtual machine that transparent-mode works. For this I wrote a dns server which can resolv the domain name via http-proxy.;-) is this parent proxy is only for https? can it intercept connections? if it is intercepting ssl connections you can mark + route any ssl connection. Regards, Eliezer -- Eliezer Croitoru https://www1.ngtech.co.il IT consulting for Nonprofit organizations eliezer at ngtech.co.il
Re: [squid-users] ACL for client_persistent_connections per User-Agent?
On 4/11/2012 2:53 a.m., Petr Tichý wrote: Hello everybody I found that while behind Squid/3.1.6 in tproxy mode, the Microsoft AutoUpdate on Mac cannot check for updates (times out). Setting client_persistent_connections off cures the problem. Would it be possible to tell squid to disable client_persistent_connections for a particular request, matching for example User-Agent header? Posisble, maybe, but that squid version is quite outdated and you will find that the current supported releases all perform connection persistence properly. Please update your Squid. Amos