<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA1 <br>
<br>
I.e,<br>
<br>
easy way to identify problem URL does not exists. Excluding user
complaints.<br>
<br>
Right?<br>
<br>
I thinking about correllation analyses between access.log and
cache.log. ;)<br>
<br>
<br>
15.01.2015 17:23, Amos Jeffries пишет:<br>
<span style="white-space: pre;">> On 16/01/2015 12:14 a.m., Yuri
Voinov wrote:<br>
><br>
> > Is it possible to know though URL, wich is got an error?<br>
><br>
><br>
> There is no URL involved.<br>
><br>
> All that has happened is that the client opened a TCP
connection to<br>
> Squid then the TLS started happening on that connection ...
and fails.<br>
><br>
> Which is why I recommend the openssl command line tool, use
it to<br>
> connect to Squid and it should report whats going on.<br>
><br>
> Amos<br>
> _______________________________________________<br>
> squid-users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
> <a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a></span><br>
<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2
<br>
<br>
iQEcBAEBAgAGBQJUt6rdAAoJENNXIZxhPexGaagH/1hSevSrH9QsTm+N8TGgjz/Z
<br>
oMxWzhbsGYBjwQpk91lkqxl9V8vJkeXPTloSPjo3tEUqWq03KW1wkh7+4ImqwQ2x
<br>
hvNmtkRntnJDYDyHvQQZeA+98kUoJKCp70Ac/Z2Ap7Dforz9Rd+PlYT18iru86D3
<br>
LyyqQ0zYtbH8qLipGy8VV8m0SttU826OVHDzCO+8JJv7pjmrge7RvkkLpLtCu3wJ
<br>
j6GYWQzz9P8rUNEOBMcy6filthcAAOiXiIWcT452lhzpAabA4FsNxgIbW8mOrfNo
<br>
Fmbg1c/JE/7H+XQ/yIgs+UCQU2OY+Z+uQczUuToYvWvcGzCKJUUPJExl+gBaabU=
<br>
=OSul
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>