On 3/15/06, Gil Freund <[EMAIL PROTECTED]> wrote: > Hi, > > If I understand apache2 correctly, I cannot use separate certificates > for virtual named based sites. This is because Apache2 cannot > determine which certificate to use prior to identifying the site, and > that cannot be achieved since the name needs to be resolved. Sort of a > catch22. > > Can anyone suggest s solution better then redirecting > (site1.example.com -> www.example.com/site1, site2.example.com -> > www.example.com/site2)?
As far as I remember this is a known problem with SSL (not just Apache) - the protocol allows exactly one secure site per TCP PORT. Here are links to Apache docs: http://httpd.apache.org/docs/1.3/vhosts/name-based.html#namevip http://httpd.apache.org/docs/2.0/vhosts/name-based.html How about allocating a separate TCP port for each site and maybe redirect from a plain HTTP concentrator: So people access ("->" stands for HTTP redirect): site1.example.com:80 -> www.example.com:443, site2.example.com:80 -> www.example.com:444, etc... ? > > Thanks > > Gil Cheers, --Amos -- "I was being prosecuted for my beliefs.... I believed people wouldn't notice I'd sold them camels with plaster teeth until I was well out of town." - Terry Pratchett, "Pyramids" ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
