Date:  Fri, 27 Oct 2006 08:45:24 +0200
From:  =?ISO-8859-1?Q?Tom_M=FCller-Kortkamp?= <tmueko (at mark) kommunity.net>
Subject:  [coba-e:07738] Re: SSL for preview addresses
To:  coba-e (at mark) bluequartz.org
Message-Id:  <BE7FDB04-17CE-4B73-BECC-65EABE7523AD (at mark) kommunity.net>
In-Reply-To:  <4541A5D8.60207 (at mark) enavn.com>
References:  <4538D22C.6080609 (at mark) enavn.com> <4541A5D8.60207 (at mark) enavn.com>
X-Mail-Count: 07738

you could configure one SSL-Site and write a Redirector with mod_rewrite

something like
rewriteCond %{REQUEST_URI} ^(\w+\.[\w-]+.\w+)$ [NC,OR]
...
rewriteRule ^/(.*) http://%1/$1


tmueko

Am 27.10.2006 um 08:23 schrieb Jes Kasper Klittum:

> Has anyone got an idea about how to get my server to listen on port  
> 443 for preview addresses, without having to do the trick below?
>
> Jes
>
> Jes Kasper Klittum wrote:
>> Is there any way to start SSL on the main server, instead of just  
>> on sites? I would like to be able to use https://servername.com/ 
>> www.somedomain.com/somefile and have this SSL encrypted with the  
>> SSL cert that I imported in the admin - however, the server is not  
>> listening on port 443, so this is not possible, Only way I have  
>> been able to do this was:
>> 1) Edit /usr/sausalito/handlers/base/vsite/unique.pl to make sure  
>> that I am able to add a site with the same name as the server.
>> 2) Import SSL cert on newly created site, and enable SSL (now port  
>> 443 is active).
>> 3) Edit /etc/httpd/conf/httpd.conf and uncomment the ServerName  
>> variable and put in the same name as the newly created site.
>> Now SSL is available for https://servername.com/www.somedomain.com/ 
>> somefil. but it seems to be an ugly hack.
>> /Jes
>
>

-- 
kommunity GmbH & Co.KG
Tom MÍler-Kortkamp
Netzwerke & Internet
Goseriede 4
D-30159 Hannover

Phone +49 (0)5 11 - 80 72 58 0
Fax +49 (0)5 11 - 80 72 58 10
http://www.kommunity.net