What is the state with TLS/SNI at the moment? We are exploring offering SSL certificates to users, and in a perfect world we would like to keep our httpd.conf free of provisioning.
Apache 2.2.0
OpenSSL-0.9.8e
At the moment, all users' vhosts are defined as:
<VirtualHost *:80>
VirtualDocumentRoot "/export/nfs/www/%-1/%-2.-1/%-2.-2/%-2+/"
So a request for http://www.example.com/$path would translate as
/export/nfs/www/com/e/l/www.example/$path
If that directory exists it is served. What would be ideal is if a user had a certificate as: /export/nfs/www/com/e/l/www.example/.certificate Then SSL TLS/SNI would use it and "everything would just work". (Minus Safari, and Konquerer from our current tests) Possible right now ? Possible if I add a little code? Lundy -- Jorgen Lundman | <lundman@xxxxxxxxxxx> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home) --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|