I read another post where you stated: "Squid does not yet know how to initiate SSL connections, only how to accept SSL connections from clients"
And from that now I am curious if my plan to have the external squid server talk ssl through a firewall to the second squid server is not going to work? We discussed this over the mailing list about a year ago, but my memory faded along with flame on the back burner..... client <SSL> SQUID1 <SSL through FIREWALL> SQUID2 <terminate SSL> webserver Thanks for your time. -----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 6:47 PM To: Markham, Richard Cc: '[EMAIL PROTECTED]' Subject: Re: [squid-users] https_port WAS: [client->SQUID1(https)->SQUID2(http)->apache] On Wed, 22 Oct 2003, Markham, Richard wrote: > Stopping squid: 2003/10/22 17:09:15| parseConfigFile: line 49 unrecognized: > 'https_port 443' > > https_port is not reconized when I try to start squid? You need to specify at least which certificate to use I think. > squid2.5stable4 > compiled with ./configure --enable-ssl What does "squid -v" return? kRegards Henrik
