By the help of God.
I think I can pinpoint the problem but I'm not sure, It looks like the
issue is between c-icap and squid communication.
>From squid logs I can see lots of traces:
2023/10/22 12:31:50.654 kid1| 93,3| ModXact.cc(556) readMore: not reading
because ICAP reply pipe is full
2023/10/2
By the help of God.
I'll clarify more when I'm looking at chrome's Internet Tools network
traffic of one of the users that several
Requests are timed out and at the same time I see in Squid's access log a
trace that according to your explanations
was opened for more that 60 secs for the timed out
On 19/10/23 01:21, Ben Goz wrote:
By the help of God.
Hi,
I saw in my access log a traces that shows that spliced URLs tunneling
is very slowly:
Please clarify what you mean by "slow" ?
How have you determined speed ?
What speed are you expecting / would you call non-slow ?
FYI, Several
By the help of God.
Hi,
I saw in my access log a traces that shows that spliced URLs tunneling is
very slowly:
18/Oct/2023:15:18:50 +0300 240841 192.168.3.98 TCP_TUNNEL/200 6225 CONNECT
beacons2.gvt2.com:443 - HIER_DIRECT/172.217.0.67 - beacons2.gvt2.com -
splice -
18/Oct/2023:15:18:50 +03006
