On Nov 20, 2007 4:48 PM, Gregor Schneider <[EMAIL PROTECTED]> wrote: > Guys, > > I've just solved the problem. > > As I said b4, I don't care about a message stating "SSL-cert is not > valid" since it's just a test-server.
That's not the issue. You can't combine namevirtualhosts with SSL. So any https request will go to your first *.443 virtualhost, regardless of what you put there as servername or serveralias. > The problem was the ServerName-directive: > > Now I've changed my vhost-definition to > > <VirtualHost *:80> > ServerAlias test-clue > .... > </VirtualHost> > > <VirtualHost *:443> > ServerAlias test-clue > .... > </VirtualHost> > > This means I did not state any ServerName-directive but used > ServerAlias instead, and everything runs like charm :) Are you sure? This looks like Apache behaving against its specification in a big way. Krist -- [EMAIL PROTECTED] [EMAIL PROTECTED] Bremgarten b. Bern, Switzerland -- A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? A: Top-posting. Q: What's the biggest scourge on plain text email discussions? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
