-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Glen,
Since openssls_client is showing you this error I assume squid
received the same response.
We do need to verify why the connection is being hangs.
For now it seems like not 100% squid related issue.
Eliezer
On 12/09/2014 01:57 AM, glenn.gr
Start Time: 1418082857
Timeout : 300 (sec)
Verify return code: 0 (ok)
-Original Message-
From: Eliezer Croitoru [mailto:elie...@ngtech.co.il]
Sent: Monday, 8 December 2014 1:21 PM
To: squid-users@lists.squid-cache.org
Cc: Glenn Groves
Subject: Re: [squid-users] https i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK Glenn,
It's unclear on what side the SSL error is.
There are issues and the next step would be to try to run some openssl
s_client test towards these hosts.
An example throw a proxy and directly can be found in the next link:
http://stackoverflow.c
>
> On IE, the error is :the proxy server is not responding"
> On Chrome: "ERR_SSL_PROTOCOL_ERROR"
> On Firefox "ssl_error_rx_record_too_long"
>
> If I bypass the proxy and go direct to the internet through our firewall, it
> works fine.
>
> This suggests to me, without having any errors in squi
nday, 8 December 2014 8:33 AM
To: squid-users@lists.squid-cache.org
Cc: Glenn Groves
Subject: Re: [squid-users] https issues for google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Glenn,
I noticed that in the mean while you have upgraded the system to latest 3.4.9
stable.
As Amos mention
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Glenn,
I noticed that in the mean while you have upgraded the system to
latest 3.4.9 stable.
As Amos mentioned there are couple options about the tunneling issues.
I am unsure about the issue since in my environment squid seems to not
have any iss
uid-cache.org
Subject: Re: [squid-users] https issues for google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/12/2014 9:48 p.m., glenn.groves wrote:
> Hi All,
>
> I have finally been able to spend time upgrading a server to a later
> squid version, I have tried 3.4.9.
>
> I co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/12/2014 9:48 p.m., glenn.groves wrote:
> Hi All,
>
> I have finally been able to spend time upgrading a server to a
> later squid version, I have tried 3.4.9.
>
> I could not get authentication to work for this test, but proceeded
> to test with
...@bradnams.com.au
Sent: Thursday, 9 October 2014 9:04 AM
To: elie...@ngtech.co.il; squid-users@lists.squid-cache.org
Subject: Re: [squid-users] https issues for google
Hi Eliezer,
The DNS we are using is the ISP default for external, our internal domain DNS
for internal. Nslookup works for all
-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Amos Jeffries
Sent: Friday, 10 October 2014 3:16 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] https issues for google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glenn, I just had a brainstorm.
Your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glenn, I just had a brainstorm.
Your version is 3.1 so you are probably suffering from
http://bugs.squid-cache.org/show_bug.cgi?id=3371
This bug shows up particularly badly when SPDY, WebSockets or HTTP/2
is being attempted by the browser.
If so you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/2014 12:02 p.m., glenn.gro...@bradnams.com.au wrote:
> I was able to capture the log at the time this happened to me, I
> got the following in the access.log:
>
> 1412895309.389 84 10.10.10.69 TCP_MISS/200 0 CONNECT
> www.youtube.com:443
formation.
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of glenn.gro...@bradnams.com.au
Sent: Thursday, 9 October 2014 9:04 AM
To: elie...@ngtech.co.il; squid-users@lists.squid-cache.org
Subject: Re: [squid-users] https issues for g
...@ngtech.co.il; squid-users@lists.squid-cache.org
Subject: Re: [squid-users] https issues for google
Hi Eliezer,
The DNS we are using is the ISP default for external, our internal domain DNS
for internal. Nslookup works for all tests.
I would like to update to the latest stable, but I am concerned of
[mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Eliezer Croitoru
Sent: Wednesday, 8 October 2014 7:39 AM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] https issues for google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Glenn,
Since you are not using intercept or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Glenn,
Since you are not using intercept or tproxy the basic place to look at
is the access.log.
You can see there if the proxy is trying for example to reach an IPV6
address (by mistake).
Also to make sure there is an issue you can use specific
PM
To: Glenn Groves
Cc: squid-us...@squid-cache.org
Subject: Re: [squid-users] https issues for google
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
glenn.gro...@bradnams.com.au wrote:
>
> We have a weird issue where https sites apparently don't respond (get
> message "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
glenn.gro...@bradnams.com.au wrote:
>
> We have a weird issue where https sites apparently don't respond
> (get message "this page can't be displayed"). This mainly affects
> google websites and to a lesser affect youtube.
But if you switch off pro
Either find the error from the log file or run tcpdump to capture the
traffic to start with.
- CW
On 10/7/2014 11:51 AM, glenn.gro...@bradnams.com.au wrote:
Hi All,
We have a weird issue where https sites apparently don't respond (get message "this
page can't be displayed"). This mainly affec
Hi All,
We have a weird issue where https sites apparently don't respond (get message
"this page can't be displayed"). This mainly affects google websites and to a
lesser affect youtube. It has been reported it may have affected some banking
sites but this is unconfirmed. We are running centos
20 matches
Mail list logo
