Re: [squid-users] How te deal with proxy authentication bypass

2020-09-28 Thread Service MV
In my case I have the domains, for example from webex, which I get from their official support page. It seems that I am doing something wrong or I am not understanding well. I base on this documentation https://wiki.squid-cache.org/ConfigExamples/Authenticate/Bypass The error I get is 407. I under

Re: [squid-users] measuring latency of squid in different scenarios

2020-09-28 Thread Alex Rousskov
On 9/28/20 9:19 AM, Rafał Stanilewicz wrote: > I'd like to get some numbers about squid-introduced latency of getting > some particular web resource. Is there any benchmarking program I could > use? I'd like to see what is the current latency of getting the resource > without any proxying, then of

Re: [squid-users] squid 5.0.4 cache_peer bug on https outgoing

2020-09-28 Thread openwrt
It worked. thanks. Alex Rousskov 于2020年9月28日周一 下午9:52写道： > On 9/28/20 5:39 AM, openwrt wrote: > > > The bug is that cache_peer https CONNECT drops the port number > > Please try the attached patch. > > Thank you, > > Alex. > > > > squid cache_peer https CONNECT packet. > > > > CONNECT d.qqq.win

Re: [squid-users] [ext] Re: Change of server hardware (?) resulted in massive increase of crashes

2020-09-28 Thread Ralf Hildebrandt
> This is still bug #5055. I hope we will post an official pull request > properly addressing it soon. > > In my environment, Squid v5 is hardly usable without those fixes but, as > you know, YMMV. Your OS upgrade could trigger different DNS resolution > timings, the new cluster may have different

Re: [squid-users] squid 5.0.4 cache_peer bug on https outgoing

2020-09-28 Thread Alex Rousskov
On 9/28/20 5:39 AM, openwrt wrote: > The bug is that cache_peer https CONNECT drops the port number Please try the attached patch. Thank you, Alex. > squid cache_peer https CONNECT packet. > > CONNECT d.qqq.win  HTTP/1.1 (bad format: without port) > > 0040   d1 d8 43 4f 4e 4e 45 43 54 20 64

[squid-users] measuring latency of squid in different scenarios

2020-09-28 Thread Rafał Stanilewicz
Hello, I'm planning the deployment of web proxy in my environment. It's not very big, around 80 typical windows 10 workstations, active directory, plus some DMZ servers. For now, there is very basic L7 inspection on the edge firewall. I plan to use two separate squid instances, one for explicit p

Re: [squid-users] squid 5.0.4 cache_peer bug on https outgoing

2020-09-28 Thread Amos Jeffries
On 28/09/20 10:39 pm, openwrt wrote: > I located the bug and found a another way to deal with it. > > The bug is that cache_peer https CONNECT drops the port number > > If you do the compatibility treatment on the back of the agent software, > you can solve this problem > > However, it would be

Re: [squid-users] squid 5.0.4 cache_peer bug on https outgoing

2020-09-28 Thread Amos Jeffries
On 28/09/20 6:41 pm, openwrt wrote: > Yes, I've tried all of these combinations. > > ### 0x00 cache_peer no ssl > >> ssl_bump allow all "allow" is not a SSL-Bump action type for any version of Squid. AFAIK, SSL-Bump falls back to

Re: [squid-users] squid 5.0.4 cache_peer bug on https outgoing

2020-09-28 Thread openwrt
I located the bug and found a another way to deal with it. The bug is that cache_peer https CONNECT drops the port number If you do the compatibility treatment on the back of the agent software, you can solve this problem However, it would be best if it was resolved on squid. ### 0x01 wireshare