Re: https admin?

Simon Rönnqvist wrote:

> But when using traditional name-based virtualhosts (specified in  
> httpd.conf) it'll lead you to the main host as soon as you use https...

Yes.

> Would this somehow be possible to overcome using modrewrite? That  sound 
> kind of revolutionary to me, not only for Flux CMS but for the  web as a 
> whole. :-)

Well - as I stated before, my setup uses the *same* certificate for 
*all* domains. That's not a problem in my case, because all the domains 
I serve SSL for are all subdomains of my main domain. So I just 
generated a wildcard certificate at http://cacert.org and set it up on 
my webserver.

In a real setup you would of cause wanted to have more than one 
certificate - in most cases on per client - and then one IP per certificate.

But you asked for a solution on how to solve the HTTPS admin problem and 
I think that what I suggested would just do it.

> Isn't it so that it's not technically possible for the webserver to  
> know which domainname you actually entered when using https? It'll  only 
> know IP, right?

There is some chicken and egg problem described here*: 
http://httpd.apache.org/docs/1.3/vhosts/name-based.html

*note: This applies in the case you have more than one certificate.

> Could you show me a working example?

Here we go:

- I use apache 1.3 with mod_ssl
- The CN of my cert. is *.mydomain.ch

# enable named virtual hosts for port 443(SSL)
NameVirtualHost 123.123.123.233:443

# first SSL virtual host
<VirtualHost first.mydomain.ch:443>
   # enable ssl for this virtual host
   SSLEnable
   DocumentRoot /var/www/first/htdocs
</VirtualHost>

# 2nd SSL virtual host
<VirtualHost 2nd.mydomain.ch:443>
   # enable ssl for this virtual host
   SSLEnable
   DocumentRoot /var/www/2nd/htdocs
</VirtualHost>



HTH
Philipp
-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms