Further thought...on how we are setting it up. One ssl cert for www.mycompany.com, resides on the proxy.
Internet-end-user -->ssl-->rp-->non-ssl ldap-authenticated traffic --> back end webserver With the redirect for each of the back end webservers, you can have a single cert. You can not have a single cert for two different domains though, (mycompany.com and mycompany2.com need different certs) mycompany.com/intranet and mycompany.com/extranet can use the same cert. Chris Perreault -----Original Message----- From: Francois Liot [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 8:49 AM To: Dan DeLong Cc: [EMAIL PROTECTED] Subject: Re: [squid-users] reverse proxy / virtual hosting As far as I know SSL standart it's unfortunatelly impossible. Apache is suffering of the same limitation. Regards Francois Liot On Tue, 2004-06-22 at 14:42, Dan DeLong wrote: > Hello, > > I currently have squid running as a reverse proxy. I have a number of > squid instances running to handle a number of different websites. > Each squid instance listens on it's own ip address and handles the SSL > cert for the incoming web request. My goal is to have squid listen on > one address to handle multiple websites in essence do virtual hosting. > Can this be done with squid ? If so, can you provide any direction on > how to set squid up to do this ? > > Thanks. > >
