On 17 Mar 2003, Joon Guillen wrote:
> > https://www.yourowndomain.com/company2 > > https://www.yourowndomain.com/company3 > > > > I know it's kludgy... > > Yes it is, and I don't think clients would be happy with that setup. :P > eh how about: company1.domain.com company2.domain.com company3.domain.com but you will need a wildcard cert instead (*.domain.com) for all of them. > I did some further reading, and as far as I can tell, the issue about > the IP addresses resides on the client (browser). That, if a browser > has already mapped the IP address with a particular SSL certificate, it > won't allow any other certificate with the same IP address. > i think it's the webserver and not the browser. anyway, during the SSL handshake, the webserver wont yet see the url's domain so there's no point in maintaining multiple certs per IP/port hoping to match the url's domain to one of the certs. pong _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
