Hello all,
just wondering whether it is possible to perform SSLBump/SSLSplit for
non-HTTPs connections. At the moment we are interested in FTPs.
We are running Squid 3.4.2 version.
Configured the SSLBump and in that case not able to receive SSL Certificates
proxy:/etc/squid3# grep server-first sq
No worries—thanks for following up on it!
That’s very interesting, about the concurrent requests, because the “normal”
report does around 80% more requests per day than the “leaky” one — a few
hundred thousand vs a couple of million.
Does this CLOSE_WAIT sockets issue have a bug being tracked o
ers@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
--
End of squid-users Digest, Vol 21, Issue 101
-- next part --
An HTML attachment was scrubbed...
URL: <
http:/
Hey Amos,
I am trying to apply patch but it fails to apply for both hunks. It seems the
source code is different .
I am using latest squid version src code 3.5.19
Can you send patch from the latest one or let me know which version you are
using.
Thanks
_
On 24/05/2016 5:44 p.m., Dan Charlesworth wrote:
> Gentle bump 😁
>
>
Hi Dan,
sorry RL getting in the way these weeks.
Two things stand out for me.
Its a bit odd that exteral ACL entries shodul be so high. But your
"normal" report has more allocated than the "leaky" report. So thats
just a sig
On 31/05/2016 9:56 p.m., Tomas Mozes wrote:
> On Thu, May 26, 2016 at 8:04 AM, Amos Jeffries wrote:
>
>> On 24/05/2016 7:52 p.m., Tomas Mozes wrote:
>>> Hello,
>>> on two different squid servers I've observed a crash of pinger. First it
>>> appeared on version 3.5.15 and later on version 3.5.17.
>
On 1/06/2016 9:05 a.m., Aashima Madaan wrote:
> Hey Amos,
>
>> What is causing the problem is that ICAP services need to be working
>> *immediately* and do not wait for DNS results to come back. If they are
>> not available immediately then the service is not contactable for that
>> transaction.
>
On 1/06/2016 6:20 p.m., SLeipold wrote:
> Dear squid-users,
>
> at first:
> thanks for adding me to your mailing list.
> My question is about the cache_peer configuration directive.
>
First problem. No. Your question is about acces controls and ACL processing.
> In my config I have to use thre
Cleared cache with disabled collapsed forwarding:
2016/06/01 14:36:37 kid1| clientProcessHit: Vary object loop!
2016/06/01 14:36:37 kid1| varyEvaluateMatch: Oops. Not a Vary match on
second attempt, 'http://egov.kz/wps/theme/jq/mistakes.js'
'accept-encoding="gzip,%20deflate"'
2016/06/01 14:36
