[squid-users] How to configure Icap can improve the performance of proxy?

[赵 俊]

My Squid  with configuration of Icap like this:


 #icap
icap_enable on
icap_preview_enable on
icap_preview_size 1024
icap_send_client_ip on
adaptation_meta X-Client-Port "%>p"
icap_206_enable on
icap_persistent_connections off


icap_service service_req reqmod_precache 0 icap://192.168.10.200:1344/echo
icap_service service_res respmod_precache 1 icap://192.168.10.200:1344/echo
adaptation_access service_res allow all
adaptation_access service_req allow all


When I configured the Icap parameter of Squid , the number of new connection or 
the number of concurrent connections  was less than half as only Squid running.
So how to configure Icap can improve the performance of proxy?

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Proxy through another proxy possible?

[Eliezer Croitoru]

Hey Amos,

Would a PROXY protocol based "router" or "load balancer" be fine also?
I tested the PROXY protocol v1 against squid v3.5 at the time and It was 
working very well.
I believe that if the requirement is to be able to route specific clients to a 
specific proxy it should  be or might be done with as lowest CPU as possible.
It will however change for the case when the local proxy also needs to process 
specific traffic.

Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il


-Original Message-
From: squid-users  On Behalf Of Amos 
Jeffries
Sent: Saturday, April 7, 2018 09:31
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Proxy through another proxy possible?

On 07/04/18 18:02, xpro wrote:
> Would it be done like below?
> 
> http_port 3001
> acl port1 myport 3001
> tcp_outgoing_address myotherproxy.com:3114 port1
> 
> 
> I want anyone connecting to my proxy using port 3001, to use the the
> proxy server on myotherproxy.com:3114

No. tcp_outgoing_address is the IP your Squid uses on its outgoing TCP
connections.

cache_peer is for configuring destination details about any specific
peer (upstream server or proxy) to relay messages through.
 see 

Amos


> 
> 
> On 04/07/2018 01:05 AM, Amos Jeffries wrote:
>> On 07/04/18 11:34, xpro wrote:
>>> I'm not sure if Squid is the right tool for this. I'm trying to achieve
>>> the following.
>>>
>>> I would have access to some exclusive proxies, but I would like for a
>>> limited amount of people to use these proxies without getting the
>>> original proxy IP. I want them to go through my proxy server and then my
>>> proxy server would forward them to the proxy I use.
>>>
>>>
>>> Would this be possible with Squid?
>> Of course. I'm not exactly clear on what you mean by original or
>> exclusive proxies, but HTTP and Squid are certainly able to chain.
>>
>> Amos
>> ___
>> squid-users mailing list
>> squid-users@lists.squid-cache.org
>> http://lists.squid-cache.org/listinfo/squid-users
> 
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Rafael Akchurin]

Hello Roberto,

When Squid is "slow" like users complain first thing to check is always the DNS 
settings.
Also sometimes switching to "IPv4 DNS resolve first" helps.

Look for "squidclient mgr:idns" and "dns_v4_first on" on Squid wiki.

Hope others have better answers.

Best regards,
Rafael Akchurin
Diladele B.V.

https://www.diladele.com/


-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf 
Of Roberto Carna
Sent: Monday, April 9, 2018 9:59 PM
To: Antony Stone 
Cc: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid is very slow after moving to production 
environment

Dear Antony, both proxies are virtual machines in the same DMZthey use the 
same DNS, the same firewall, the same Internet link, the same IP but different 
MAC Address.

Firewall rules are the same too.

The new proxy is slow because when users try to go to a web page, it is very 
slow in download the content page.about 1 minute to do it.

The Dansguardian configuration is te same too.

I've past my configuration in the previous mail.

Thanks a lot !!!



2018-04-09 16:36 GMT-03:00 Antony Stone :
> On Monday 09 April 2018 at 21:00:21, Roberto Carna wrote:
>
>> Dear, I have implemented a server with Dansguardian 10.2.1.1 and 
>> Squid 3.5.23-5.
>>
>> I've tested it with 5 users for along 2 months and always it worked OK.
>>
>> But today when a moved it to production environment, it worked but 
>> very very slow.
>
> 1. What is "very very slow"?  What difference are you noticing:
>
>  - limited bandwidth for downloads?
>
>  - high latency for reaching new URLs?
>
>  - reduced ability to handle new requests?
>
> Basically, how are you measuring the difference between test 
> performance and production performance?
>
> 2. Please explain your networking setups for the test and production
> environments:
>
>  - do they share the same Internet connection?
>
>  - do they both go through the same firewall?
>
>  - do they both use the same DNS server, or have their own DNS 
> servers, or what?
>
>  - are the same traffic rules implemented for each procy on the firewall/s?
>
>  - do you use any form of user authentication, and if so, please give 
> details
>
> 3. What volume of requests per hour / minute / day / whatever is 
> convenient did you have in the test environment, and what volume do 
> you have now in the production environment?
>
>> I've just changed hostname and IP, in order to match with the old 
>> proxy server and flush de ARP table of the firewall (because ths 
>> server has the same IP but different MAC Address)and no more. And 
>> let me say that in production environment, there are 30-40 users at 
>> all, it's not a big number of users at all.
>>
>> Where can I start to see in order to analyze the problem? Any idea to 
>> help me?
>
>
> Regards,
>
>
> Antony.
>
> --
> I thought I had type A blood, but it turned out to be a typo.
>
>Please reply to the list;
>  please *don't* CC me.
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Periko Support]

Try to add this setting:

dns_v4_first on

Latter check settings and see if there is no issue with the setting.

squid -k parse.

Then reload:

squid -k reconfigure

Test.


On Mon, Apr 9, 2018 at 1:05 PM, Antony Stone
 wrote:
> On Monday 09 April 2018 at 21:58:52, Roberto Carna wrote:
>
>> Dear Antony, both proxies are virtual machines in the same DMZthey
>> use the same DNS, the same firewall, the same Internet link, the same
>> IP but different MAC Address.
>
> So, what is different between "test" and "production"?
>
>
> Antony.
>
> --
> "Remember: the S in IoT stands for Security."
>
>  - Jan-Piet Mens
>
>Please reply to the list;
>  please *don't* CC me.
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Antony Stone]

On Monday 09 April 2018 at 21:53:26, Roberto Carna wrote:

> I've just changed the new proxy to test environment and it works very
> well againI get lost.

What does that change involve?  I'm trying to understand what is different 
between your "test" environment and your "production" environment, especially 
since you say they both have the same IP address.


Antony.

-- 
A user interface is like a joke.
If you have to explain it, it means it doesn't work.

   Please reply to the list;
 please *don't* CC me.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Antony Stone]

On Monday 09 April 2018 at 21:58:52, Roberto Carna wrote:

> Dear Antony, both proxies are virtual machines in the same DMZthey
> use the same DNS, the same firewall, the same Internet link, the same
> IP but different MAC Address.

So, what is different between "test" and "production"?


Antony.

-- 
"Remember: the S in IoT stands for Security."

 - Jan-Piet Mens

   Please reply to the list;
 please *don't* CC me.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Roberto Carna]

Dear Antony, both proxies are virtual machines in the same DMZthey
use the same DNS, the same firewall, the same Internet link, the same
IP but different MAC Address.

Firewall rules are the same too.

The new proxy is slow because when users try to go to a web page, it
is very slow in download the content page.about 1 minute to do it.

The Dansguardian configuration is te same too.

I've past my configuration in the previous mail.

Thanks a lot !!!



2018-04-09 16:36 GMT-03:00 Antony Stone :
> On Monday 09 April 2018 at 21:00:21, Roberto Carna wrote:
>
>> Dear, I have implemented a server with Dansguardian 10.2.1.1 and Squid
>> 3.5.23-5.
>>
>> I've tested it with 5 users for along 2 months and always it worked OK.
>>
>> But today when a moved it to production environment, it worked but
>> very very slow.
>
> 1. What is "very very slow"?  What difference are you noticing:
>
>  - limited bandwidth for downloads?
>
>  - high latency for reaching new URLs?
>
>  - reduced ability to handle new requests?
>
> Basically, how are you measuring the difference between test performance and
> production performance?
>
> 2. Please explain your networking setups for the test and production
> environments:
>
>  - do they share the same Internet connection?
>
>  - do they both go through the same firewall?
>
>  - do they both use the same DNS server, or have their own DNS servers, or
> what?
>
>  - are the same traffic rules implemented for each procy on the firewall/s?
>
>  - do you use any form of user authentication, and if so, please give details
>
> 3. What volume of requests per hour / minute / day / whatever is convenient
> did you have in the test environment, and what volume do you have now in the
> production environment?
>
>> I've just changed hostname and IP, in order to match with the old proxy
>> server and flush de ARP table of the firewall (because ths server has the 
>> same
>> IP but different MAC Address)and no more. And let me say that in
>> production environment, there are 30-40 users at all, it's not a big number
>> of users at all.
>>
>> Where can I start to see in order to analyze the problem? Any idea to help
>> me?
>
>
> Regards,
>
>
> Antony.
>
> --
> I thought I had type A blood, but it turned out to be a typo.
>
>Please reply to the list;
>  please *don't* CC me.
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Roberto Carna]

Dear Periko, so here is what you ask to me:

CPU x 8
RAM x 12 GB
HD x 50 GB

And this is /etc/squid/squid.conf file:

acl SSL_ports port 443
acl Safe_ports port 80# http
acl Safe_ports port 21# ftp
acl Safe_ports port 443# https
acl Safe_ports port 70# gopher
acl Safe_ports port 210# wais
acl Safe_ports port 1025-65535# unregistered ports
acl Safe_ports port 280# http-mgmt
acl Safe_ports port 488# gss-http
acl Safe_ports port 591# filemaker
acl Safe_ports port 777# multiling http
acl CONNECT method CONNECT
coredump_dir /var/spool/squid
refresh_pattern ^ftp:144020%10080
refresh_pattern ^gopher:14400%1440
refresh_pattern -i (/cgi-bin/|\?) 00%0
refresh_pattern .020%4320
http_port localhost:3128
cache_mem 4096 MB
maximum_object_size_in_memory 4096 KB
cache_replacement_policy heap LFUDA
memory_replacement_policy lru
maximum_object_size 10 MB
cache_dir aufs /var/spool/squid 25000 16 256
cache_swap_low 90
cache_swap_high 95
access_log /var/log/squid/access.log squid
access_log syslog:local7.info
cache_log /var/log/squid/cache.log
cache_store_log /var/log/squid/store.log
store_dir_select_algorithm least-load
positive_dns_ttl 8 hours
negative_dns_ttl 30 seconds
ipcache_size 4096
ipcache_low 90
ipcache_high 95
ftp_passive on
ftp_epsv off
fqdncache_size 4096
cache_effective_user proxy
cache_effective_group proxy
httpd_suppress_version_string on
visible_hostname proxy.company.com.ar
via off
hosts_file /etc/hosts
ignore_unknown_nameservers on
request_header_max_size 64 KB
icp_port 0
htcp_port 0
icp_access deny all
htcp_access deny all
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl netadmin src 10.8.6.3/32
http_access allow manager localhost
http_access allow manager netadmin
http_access deny manager
auth_param basic program /usr/lib/squid/squid_ldap_auth -b
"dc=company,dc=com,dc=ar" -f "uid=%s" -h ldap.company.com.ar -v 3
auth_param basic children 5
auth_param basic realm COMPANY
auth_param basic credentialsttl 4 hours
auth_param basic casesensitive on
acl LDAP proxy_auth REQUIRED
http_access allow LDAP
http_access deny all
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1
acl SSL_ports port 443
acl Safe_ports port 80# http
acl Safe_ports port 21# ftp
acl Safe_ports port 443# https
acl CONNECT method CONNECT
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access deny to_localhost
http_access allow localhost
acl QUERY urlpath_regex cgi-bin \? \.css \.asp \.aspx
cache deny QUERY
acl gedo dstdomain .gde.gob.ar
always_direct allow gedo
acl GOB url_regex .com.ar
http_access allow GOB
acl NOFLASH urlpath_regex .+\.swf$
http_access deny NOFLASH
http_access deny all

I've just changed the new proxy to test environment and it works very
well againI get lost.

Thanks a lot !!!

2018-04-09 16:04 GMT-03:00 Periko Support :
> Hi, show the config file please and specs of the machine.
>
> On Mon, Apr 9, 2018 at 12:00 PM, Roberto Carna  
> wrote:
>> Dear, I have implemented a server with Dansguardian 10.2.1.1 and Squid 
>> 3.5.23-5.
>>
>> I've tested it with 5 users for along 2 months and always it worked OK.
>>
>> But today when a moved it to production environment, it worked but
>> very very slow. I've just changed hostname and IP, in order to match
>> with the old proxy server and flush de ARP table of the firewall
>> (because ths server has the same IP but different MAC Address)and
>> no more. And let me say that in production environment, there are
>> 30-40 users at all, it's not a big number of users at all.
>>
>> Where can I start to see in order to analyze the problem? Any idea to help 
>> me?
>>
>> Thanking in advance, regards !!!
>>
>> Robert
>> ___
>> squid-users mailing list
>> squid-users@lists.squid-cache.org
>> http://lists.squid-cache.org/listinfo/squid-users
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Antony Stone]

On Monday 09 April 2018 at 21:00:21, Roberto Carna wrote:

> Dear, I have implemented a server with Dansguardian 10.2.1.1 and Squid
> 3.5.23-5.
> 
> I've tested it with 5 users for along 2 months and always it worked OK.
> 
> But today when a moved it to production environment, it worked but
> very very slow.

1. What is "very very slow"?  What difference are you noticing:

 - limited bandwidth for downloads?

 - high latency for reaching new URLs?

 - reduced ability to handle new requests?

Basically, how are you measuring the difference between test performance and 
production performance?

2. Please explain your networking setups for the test and production 
environments:

 - do they share the same Internet connection?

 - do they both go through the same firewall?

 - do they both use the same DNS server, or have their own DNS servers, or 
what?

 - are the same traffic rules implemented for each procy on the firewall/s?

 - do you use any form of user authentication, and if so, please give details

3. What volume of requests per hour / minute / day / whatever is convenient 
did you have in the test environment, and what volume do you have now in the 
production environment?

> I've just changed hostname and IP, in order to match with the old proxy
> server and flush de ARP table of the firewall (because ths server has the same
> IP but different MAC Address)and no more. And let me say that in
> production environment, there are 30-40 users at all, it's not a big number
> of users at all.
> 
> Where can I start to see in order to analyze the problem? Any idea to help
> me?


Regards,


Antony.

-- 
I thought I had type A blood, but it turned out to be a typo.

   Please reply to the list;
 please *don't* CC me.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid is very slow after moving to production environment

[Periko Support]

Hi, show the config file please and specs of the machine.

On Mon, Apr 9, 2018 at 12:00 PM, Roberto Carna  wrote:
> Dear, I have implemented a server with Dansguardian 10.2.1.1 and Squid 
> 3.5.23-5.
>
> I've tested it with 5 users for along 2 months and always it worked OK.
>
> But today when a moved it to production environment, it worked but
> very very slow. I've just changed hostname and IP, in order to match
> with the old proxy server and flush de ARP table of the firewall
> (because ths server has the same IP but different MAC Address)and
> no more. And let me say that in production environment, there are
> 30-40 users at all, it's not a big number of users at all.
>
> Where can I start to see in order to analyze the problem? Any idea to help me?
>
> Thanking in advance, regards !!!
>
> Robert
> ___
> squid-users mailing list
> squid-users@lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

[squid-users] Squid is very slow after moving to production environment

[Roberto Carna]

Dear, I have implemented a server with Dansguardian 10.2.1.1 and Squid 3.5.23-5.

I've tested it with 5 users for along 2 months and always it worked OK.

But today when a moved it to production environment, it worked but
very very slow. I've just changed hostname and IP, in order to match
with the old proxy server and flush de ARP table of the firewall
(because ths server has the same IP but different MAC Address)and
no more. And let me say that in production environment, there are
30-40 users at all, it's not a big number of users at all.

Where can I start to see in order to analyze the problem? Any idea to help me?

Thanking in advance, regards !!!

Robert
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] unique access.log for specific ACLs

[Matus UHLAR - fantomas]

On 09.04.18 14:10, Joey Officer wrote:

Apologies if this has been covered before, but I could not find an archived
discussion on the same topic.  Is it possible to assign a unique log file
output to a specific ACL?  The use case is that we've begun blocking
certain sites and we would like to begin logging the attempted access.

I'd suspect something similar to the following:

(squid 3.5.12)
#blocking
acl isf_blacklist dstdom_regex "/etc/squid/block.txt"


note that dstdom_regex is quite infeffective (although not as much
as url_regex), since regulatrr expression matching is CPU hungry.
use dstdomain whenever possible.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Christian Science Programming: "Let God Debug It!".
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] unique access.log for specific ACLs

[Alex Rousskov]

On 04/09/2018 08:10 AM, Joey Officer wrote:
> Apologies if this has been covered before, but I could not find an
> archived discussion on the same topic.  Is it possible to assign a
> unique log file output to a specific ACL?

Yes, it is. See your own example below for a sketch.

> acl isf_blacklist dstdom_regex "/etc/squid/block.txt"
> access_log daemon:/var/log/squid/blocked.log isf_blacklist
> http_access deny isf_blacklist
> deny_info TCP_RESET isf_blacklist


However, please note that ACLs are evaluated in a particular directive
context so their evaluation results may change even within one HTTP
transaction scope. For example, a given ACL that did not match in
http_access rules may match when access_log rules are evaluated. There
was a more detailed discussion about that a few days ago:

http://lists.squid-cache.org/pipermail/squid-users/2018-April/018017.html


HTH,

Alex.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Re: [squid-users] Squid4 ICAP connection handling

[Alex Rousskov]

On 04/09/2018 06:03 AM, Peter Viskup wrote:
> Running Squid 4.0.23 the ICAP connections getting "frozen".
> 
> proxy:~ $ netstat -ntpa| grep 40620
> tcp   920144  0 127.0.0.1:40620 127.0.0.1:1344
> ESTABLISHED 1165/(squid-1)
> tcp0 2744857 127.0.0.1:1344  127.0.0.1:40620
> ESTABLISHED 1211/esets_icap
> 
> # after ICAP service restart
> proxy:~ $ netstat -ntpa| grep 40620
> tcp   920144  0 127.0.0.1:40620 127.0.0.1:1344
> ESTABLISHED 1165/(squid-1)
> tcp0 2744858 127.0.0.1:1344  127.0.0.1:40620
> FIN_WAIT1   -
> 
> # later on - squid still keep the connection open
> proxy:~ $ netstat -ntpa| grep 40620
> tcp   920144  0 127.0.0.1:40620 127.0.0.1:1344
> ESTABLISHED 1165/(squid-1)

> How the ICAP connections are handled?

The question is too general to give a brief useful answer.


> Was there any change in the code? 

Yes, a lot of code has changed between Squid v3 and v4, including some
ICAP-related changes.


> We didn't experienced this with Squid3.5 before.

Is there an HTTP transaction associated with (e.g., waiting for) that
stuck ICAP connection?

Can you reproduce this problem with a single HTTP transaction? Or does
it take many transactions to get Squid into this state? If you can
easily reproduce, I recommend filing a bug report with an ALL,9 trace of
the problematic transaction attached.

Alex.
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

[squid-users] unique access.log for specific ACLs

[Joey Officer]

Apologies if this has been covered before, but I could not find an archived 
discussion on the same topic.  Is it possible to assign a unique log file 
output to a specific ACL?  The use case is that we've begun blocking certain 
sites and we would like to begin logging the attempted access.

I'd suspect something similar to the following:

(squid 3.5.12)
#blocking
acl isf_blacklist dstdom_regex "/etc/squid/block.txt"
access_log daemon:/var/log/squid/blocked.log isf_blacklist
http_access deny isf_blacklist
deny_info TCP_RESET isf_blacklist

Appreciate any guidance that can be provided.

Joey

___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

[squid-users] Squid4 ICAP connection handling

[Peter Viskup]

Running Squid 4.0.23 the ICAP connections getting "frozen".

proxy:~ $ netstat -ntpa| grep 40620
tcp   920144  0 127.0.0.1:40620 127.0.0.1:1344
ESTABLISHED 1165/(squid-1)
tcp0 2744857 127.0.0.1:1344  127.0.0.1:40620
ESTABLISHED 1211/esets_icap

# after ICAP service restart
proxy:~ $ netstat -ntpa| grep 40620
tcp   920144  0 127.0.0.1:40620 127.0.0.1:1344
ESTABLISHED 1165/(squid-1)
tcp0 2744858 127.0.0.1:1344  127.0.0.1:40620
FIN_WAIT1   -

# later on - squid still keep the connection open
proxy:~ $ netstat -ntpa| grep 40620
tcp   920144  0 127.0.0.1:40620 127.0.0.1:1344
ESTABLISHED 1165/(squid-1)

How the ICAP connections are handled?
Was there any change in the code? We didn't experienced this with
Squid3.5 before.

Peter
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users