Re: sslREAD errors?

As I have said several times already: these messages can be ignored
unless someone complains about SSL failures. The error is expected in
normal operation.

If you do not want to see it, then change the loglevel of this message
to 2. The message are found in ssl.c.

Detail:
change
        debug(50, 1) ("sslReadClient: FD %d: read failure: %s\n",
to
        debug(50, 2) ("sslReadClient: FD %d: read failure: %s\n",

Or if you'd like to be really advanced and only ignore "Connection
reset" errors:
        debug(50, errno != ECONNRESET ? 1 : 2) ("sslReadClient: FD %d:
read failure: %s\n",

You probably want to do the same for the corresponding sslWriteClient
error. "Connection reset by peer" is expected to be seen in both
sslReadClient and sslWriteClient when a SSL connection is aborted by the
browser, for example if the user opens a https page and clicks on a link
while images are loading.

--
Henrik Nordstrom
Spare time Squid hacker
Gert-Jan Looy wrote:
> how do I get rid of this:  (tail of cache.log) ?
> 
> 1999/07/04 21:45:11— sslReadClient: FD 68: read failure: (131)
> Connection reset by peer
> 1999/07/04 21:45:12— sslReadClient: FD 75: read failure: (131)
> Connection reset by peer
[...]
> 
> I've even rebooted the whole machine, no difference...
> But nobody is complaining that things don't work...:-)