Hi Aaron,

As I uderstand, the docks say you can't have name based virtual hosts
because SSL is alreday serving the page before apache sees any http

In the example I posted, https://mail.mydomain.net works and takes me
to my webmail, and https://machinename.mydomain.net works and takes
me to my main webpage, however https://<anythingelse>.nydomain.net or
https://www.mydomain.net refuses the connection.

This I don't understand. If it can see mail.mydomain.net and take me
there, and it can see machinename.mydomain.net and take me there why
can't it take me to www.mydomain.net?

All I really need is mail.mydomain.net to take me to my webmail, and
anything else to just go to htdocs as normal. Can I set this up with
just one virtual host, and then some sort of catch all filter for
everything else?


--- Aaron Dalton <[EMAIL PROTECTED]> wrote:

> Glyn Astill wrote:
> > Hi people,
> > 
> > So I got ssl started, and now I'm trying to sort out my virtual
> hosts
> > but I can't seem to get them to work.
> > 
> Due to the fundamental nature of SSL and virtual host resolution
> one may
> not have more than one SSL-enabled virtual host per IP:port
> combination.
> http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#vhosts
> -- 
> Aaron Dalton       |   Super Duper Games
> [EMAIL PROTECTED]   |   http://superdupergames.org

Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for
your free account today 
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      modssl-users@modssl.org
Automated List Manager                            [EMAIL PROTECTED]

Reply via email to