Problem with https/SSL on Squid

Hi all list members,

Really sorry for the bouncing messages. I was just informed by an automatic
message about the situation. I will check with the postmaster to see what is
going on.

Anyway, I hope everyone has/had some good time on vacation.

I am writing for a problem that has appeared before on the list, but the
solution that was given does not seem to work in our case.
When connecting to https sites Squid-1.1.22 generates messages like the
ones below, resulting in indefinite delays

1998/08/20 20:17:38| sslReadServer: FD 38: read failure: (104) Connection
reset
by peer
1998/08/20 20:17:40| sslReadServer: FD 34: read failure: (104) Connection
reset
by peer
1998/08/20 20:17:53| sslReadClient: FD 32: read failure: (104) Connection
reset
by peer
1998/08/20 20:19:08| sslReadServer: FD 34: read failure: (104) Connection
reset
by peer
1998/08/20 20:19:09| sslReadClient: FD 29: read failure: (104) Connection
reset
by peer
1998/08/20 20:19:16| sslReadServer: FD 32: read failure: (104) Connection
reset
by peer

In previous messages the solution of a plug was given but to my
understanding plugs work for fixed host/port pairs and not as a generic
relay mechanism that is needed in the case where every user of the network
must be able to access every possible secure site.
Any suggestions to what must be done? I thought of using Apache-SSL on proxy
mode as SSL proxy to Squid. I am not sure that this will work though. Has
anybody tried that?
Is there any other solution that I should try?
This is really a problem since we do have quite a lot of https: access that
can't get through.

Best Regards,

Evaghelos.

> Dr. Evaghelos N. Tsiotsios
> Project Manager
> Archetypon S.A.
> 26 Fokidos St
> GR 11526 Athens
> tel. +301 7483324
> fax +301 7482696
> mailto:etsiot@archetypon.gr
> http://www.archetypon.gr
>
>
>
>
Received on Thu Aug 20 1998 - 10:36:20 MDT