RE: Problem with https

Have you defined "ssl_proxy"? This should be pointing to your main Squid
1.1.3 proxy.

 - MBM

 -----Original Message-----
From: Peter Olsson [SMTP:pol@leissner.se]
Sent: Wednesday, February 12, 1997 7:45 AM
To: squid-users@nlanr.net
Cc: Motley, Mark
Subject: Problem with https

We have a firewall with squid 1.1.3.

Inside this firewall we have a machine named dove, also with squid 1.1.3.
This squid has the firewall-squid as parent. Between dove and the firewall
is a heavily used connection, thus the internal squid to reduce load.

When our users use squid on dove, they can't use https becuase of:
"
ERROR
The requested URL could not be retrieved
 ------------------------------------------------------------------------
While trying to retrieve the URL: www.sebank.se:443
The following error was encountered:
*DNS name lookup failure
The system returned:
    DNS Domain 'www.sebank.se' is invalid: Host not found
(authoritative).
This means that:
    The named host probably does not exist.
 ------------------------------------------------------------------------
"

http and ftp to squid on dove works fine. If we use squid on the
firewall, https works fine.

The dove-machine has no external dns, so the errormessage is not
surprising, but normal http works fine, probably because dove
goes to its parent, which collects the information. But why doesn't
it do this with https? Does it have anything to do with:
"http_access deny CONNECT !SSL_ports" in the configuration?
Ie, the firewall-squid doesn't allow https-requests on port 80,
but the dove-squid does use port 80 when talking to its parent?

Can I solve this? How?

Thanks for your time!

Peter Olsson pol@leissner.se
Received on Sat Feb 15 1997 - 11:44:57 MST