On 10/05/18 12:31, OlegH1 wrote:
> Hi,
>
> I'm seeing some users of mine use squid proxy and cannot connect via
> WebSocket because the Upgrade and Connection headers are striped. All
> connections are over wss:// (TLS).
>
> My question is how possible that squid decrypts the packet, omit those
>
On 10/05/18 11:53, Roberto Carna wrote:
> Dear, I have Squid/Dansguardian in a Debian 9 server.
>
> My Squid packages is from Debian repo, it is the stable version:
>
> squid 3.5.23-5+deb9u1
...
>
> But when I read I notice two curious lines:
>
> systemd[1]: squid.servi
Hi,
I'm seeing some users of mine use squid proxy and cannot connect via
WebSocket because the Upgrade and Connection headers are striped. All
connections are over wss:// (TLS).
My question is how possible that squid decrypts the packet, omit those
headers and encrypt. I saw there is a "SSL bump"
Dear, I have Squid/Dansguardian in a Debian 9 server.
My Squid packages is from Debian repo, it is the stable version:
squid 3.5.23-5+deb9u1
After execute "squid -k parse" everything is OK:
# systemctl status squid
● squid.service - LSB: Squid HTTP Proxy version 3.x
Hello my setup is as follows :
Freebsd 11 Heimdal Kerberos Server and DNS properly configured (testlab
enviroment for example.com domain)
Freebsd 11 squid proxy server
Windows Client
I have created a keytab from the Kerberos Server for http/squid.example.com
Proxy server machine has no problem ki
On 09/05/18 18:36, Ilias Clifton wrote:
> Ubuntu box is able to connect to the internet ok. If client PCs are
> configured to use the Ubuntu box as proxy on port 3128 it works correctly.
>
> No hits in access.log for any transparent clients via wccp.. No network
> response at all from Ubuntu.
>
