RE: sslReadClient: FD 13: read failure: (232) Connection reset

Hmmm... but if I remove the proxy config from the customer's browser,
all works quite nicely. Something about accessing the SSL site via
Squid is wrong... like the remote server does not like something that
Squid does.

So, doesn't look as much like a client prob as a squid one. Any ideas
how I might attack debugging something like this?

Or, should I start testing 1.2beta? :-)
-Alan

-----Original Message-----
From: Michael Pelletier [mailto:mikep@comshare.com]
Sent: Tuesday, June 23, 1998 10:55 AM
To: Sparks, Alan
Cc: 'squid-users@ircache.net'
Subject: Re: sslReadClient: FD 13: read failure: (232) Connection reset

On Tue, 23 Jun 1998, Sparks, Alan wrote:

> I'm running Squid 1.1.20 + Retry here on HP/UX 10.20. Works great,
> except a problem with some sites running SSL...
>
> I'm getting occasion (but persistent) failures on some sites, with
> the message
> sslReadClient: FD 13: read failure: (232) Connection reset
> by peer logged. The customer's browser (NN 3.0x) errors out with a
> "connection refused" popup.
>
> Anyone know what this message is trying to tell me? Thanks in
> advance.

This basically means that the connection was dropped at the remote end
without closing it down properly. Usually it relates to a client that
crashes or is aborted in the middle of a dialogue with the server. I
see numerous instances of that message here, and nobody's complaining,
so I figure it can't be serious -- particularly when compared to stuff
people *do* complain about. ;-)

> Alan Sparks, IS Engineering Support
> <asparks@harris.com>
> Harris Network Support Systems, Camarillo CA (805) 389-2430

Harris, eh? Maybe you could talk Baseview Products into installing a
Squid server so my wife will have better web access at work... :-)

        -Mike Pelletier.
Received on Tue Jun 23 1998 - 11:57:18 MDT