-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm ignoring this message.
All pages are loading. This is error 131 from openssl.
12.04.15 0:09, mattatrmc пишет:
Hi Yuri,
I just got my Squid up and running on a fairly active test
environment, and
am seeing the same error printed. Did you
Hi Yuri,
I just got my Squid up and running on a fairly active test environment, and
am seeing the same error printed. Did you ever figure out what was causing
the errors? It appears that the pages that are requested are still loading,
it just appears to be happening more slowly.
Cheers,
Matt
You solve It ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-connection-on-FD-20-error--lib-0-func-0-reason-0-5-1-131-tp4669338p4669397.html
Sent from the Squid - Users mailing list archive at Nabble.com.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
131 error means:
CONNECTED(0003)
write:errno=131
- ---
no peer certificate available
- ---
No client certificate CA names sent
- ---
SSL handshake has read 0 bytes and written 148 bytes
- ---
New, (NONE), Cipher is (NONE)
Looks like something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After a bit Google-Fu ;)
I found this:
http://stackoverflow.com/questions/14770100/libssl-read-error-131-causing-an-application-crash
Is that it?
26.01.2015 23:22, Yuri Voinov пишет:
Hi gents,
who know, what this log messages mean:
when you know tell me because i asked this question before here and i didnt
get any answer
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Error-negotiating-SSL-connection-on-FD-20-error--lib-0-func-0-reason-0-5-1-131-tp4669338p4669351.html
Sent from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suggest we are asking in wrong place :)
This is OpenSSL error stack, not squid.
Also, man, which root CA bundle you are use in your installation?
27.01.2015 2:49, HackXBack пишет:
when you know tell me because i asked this question before here
