Greetings,
As we had agreed, we formatted our gateway machine and installed squid
(on Debian 8.3) this way:
apt-get install squid3
service squid3 stop
squid3 -z
service squid3 start
Also, we disabled QUIC and cleared cache on Google Chrome on all users'
machines.
And now the problem is gon
On 3/06/2016 1:35 a.m., William Ivanski wrote:
> Thank you for your quick response.
>
> First of all forgive me for the lack of information in the first
> email. I've tried to disable QUIC a few minutes ago and the problem
> persists. Follow the information requested:
>
> -> Compilation:
>
> I'v
Guys,
Antony made me realize I really have a messed up Squid installation. That's
why I tried many different approaches (ssl_crtd/ssl_db, intercept), but the
actual installation isn't configured as transparent proxy.
So I agree I need to reinstall and reconfigure everything. As soon as I
manage t
System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of William Ivanski
Sent: Thursday, June 2, 2016 4:36 PM
To: William Ivanski
Cc: squid-users@lists.squid-cache.org
Subject: Re: [squid-users
On Thursday 02 June 2016 at 15:35:10, William Ivanski wrote:
> Thank you for your quick response.
>
> First of all forgive me for the lack of information in the first
> email. I've tried to disable QUIC a few minutes ago and the problem
> persists. Follow the information requested:
>
> -> Compil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cache.log require too
02.06.2016 19:36, William Ivanski пишет:
> -> Access.log (the host 192.168.0.52 belongs to acl reqliberacaofixo):
> 1464870540.039495 192.168.0.52 TCP_MISS/301 675 GET
http://www.hotmail.com/ - HIER_DIRECT/65.55.65.188 <
-> Access.log (the host 192.168.0.52 belongs to acl reqliberacaofixo):
1464870540.039495 192.168.0.52 TCP_MISS/301 675 GET
http://www.hotmail.com/ - HIER_DIRECT/65.55.65.188 text/html
1464870550.793 10206 192.168.0.52 TCP_MISS_ABORTED/000 0 POST
http://s2.symcb.com/ - HIER_DIRECT/2600:1419:8
Thank you for your quick response.
First of all forgive me for the lack of information in the first
email. I've tried to disable QUIC a few minutes ago and the problem
persists. Follow the information requested:
-> Compilation:
I've installed squid using the following commands:
cd /usr/src
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
QUIC already unused by Google against HTTP/2. And better to do this (if
you need) at active network equipement level.
Otherwise you be forced to do this with hands on _every_ user Chrome by
legs.
02.06.2016 18:16, Sagar Malve пишет:
> Try disabl
Try disabling QUIC Protocol in Chrome and check ... in Chrome Browser :
Type : chrome://flags/ ---> find QUIC and Disable it.
It will not accept the Squid SSL Certificate unless you disable this
Protocol ...
Let us know if it works
Regards
Sagar Malve
On Thu, Jun 2, 2016 at 5:39 PM, Yuri
On Thursday 02 June 2016 at 14:03:33, William Ivanski wrote:
> I've started experiencing some problems with Google Chrome after installing
> Squid in my Network.
> Any suggestions?
Yes - tell us how you installed squid, which version you installed, which
platform (O/S and version) you installed
Any useful info? Squid version, config, logs?
Thelepaty on vacation.
02.06.2016 18:03, William Ivanski пишет:
Good time of the day!
I've started experiencing some problems with Google Chrome after
installing Squid in my Network. It gets stuck into a loop of
"Establishing secure connection".
Good time of the day!
I've started experiencing some problems with Google Chrome after installing
Squid in my Network. It gets stuck into a loop of "Establishing secure
connection". Sometimes it succeeds loading the web pages, but usually it
cannot. It's really annoying and occurs just in Chrome.
13 matches
Mail list logo