Oliver Fromme wrote:
Uzi Klein <[EMAIL PROTECTED]> wrote: > Oliver Fromme wrote: > > Uzi Klein <[EMAIL PROTECTED]> wrote:> > > Actually, SSL can not be configured per name vhost. (or at least can not > > > work)> > > Because SSL handshake is used before http headers, it just can't be done.> > > > You can configure SSL perfectly fine per virtual host,> > provided that they have separate addresses. You can > > even use SSL for virtual hosts that share an address, > > if they listen on different ports (in this case you > > can use redirects for convenience, so users don't have > > to type the port numbers).> > > > It's correct that SSL doesn't work for pure name-based> > virtual hosts (not using "special tricks"), but nobody > > was talking about that.> > > > note the *name vhost*Only _you_ were talking about named virtual hosts. :-) They are not an issue in this case. > and the user's conf.
The original post has > <VirtualHost *:80> > ServerName freebsd.domain.net > ServerAlias freebsd.domain.net > DocumentRoot /usr/local/www/data > </VirtualHost> > > ...which should be loaded on startup. Also, i activated > > NameVirtualHost *:80 But it's really getting off topic.looks like the problem has to do with DocumentRoot or DirectoryIndex in httpd.conf.
The user's configuration, as far as it has been (partially) shown, contains just two virtual hosts which run on different ports (port 80 for for HTTP and port 443 for HTTPS). So name-based virtual hosts are _not_ an issue here. Name-based virtual hosts would be a problem if you run multiple of them on the same IP address _and_ on the same port with SSL (usually 443). That's not the case here. Best regards Oliver
-- Uzi Klein Software Development Executive B.M.B.Y Software Systems LTD. Phone: 972-4-9597989 Fax: 972-3-6179336 Email: [EMAIL PROTECTED] http://www.bmby.com
smime.p7s
Description: S/MIME Cryptographic Signature
