-----Original Message----- From: Arun G Nair [mailto:arungnair@xxxxxxxxx >>> Atlast I got it working !!!! So name based virtual hosting *is* possible with mod_ssl. >> No it isn't. You only have encryption working. You do not have authentication. > Ok So what else do I need to get it working ? Or is it not possible as the docs say ? It is not possible. Note that this is not a limitation on apache or mod_ssl, it is fundamental to the way HTTP works and applies to any webserver. SSL encrypts the *entire* request, including the Host header that apache uses to decide on which VH to use. So apache can't figure out which cert to use (the SSLCertificateFile directive is *inside* the VH definition). You need to thoroughly understand how SSL negotiation works and how the SSL protocol encapsulates HTTP (you have to go through SSL to get to the HTTP layer). So anything which is part of HTTP (like the Host header) can't be used during the SSL phase. However, for name-based VHs, you need the host header to choose the cert so you're stuck. Note that apache won't just give up (maybe it should...) - it just gets the cert from the first VH. Any cert will work for encryption (just needs a public key) but it will fail for authentication since usually the common name in the cert won't match the site name in the request and the browser will, quite rightly, warn the user about this. Once the cert has been delivered and an SSL channel established, apapche can see the decrypt the requests and see the Host header and so now it *seems* to work - you get the VH you asked for. If you're in a dev setup, maybe you just ignore all the warnings and it will seem to work. To have multiple SSL hosts, you need to distinguish them at the TCP/IP layer - ie, they need to have distinct IP addresses and/or ports. So you can have: https://192.168.1.1:443 and https://192.168.1.1:444, etc or https://192.168.1.1:443 and https://192.168.1.2:443 Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. Diese E-mail ist eine private und persönliche Kommunikation. Sie hat keinen Bezug zur Börsen- bzw. Geschäftstätigkeit der SWX Gruppe. This e-mail is of a private and personal nature. It is not related to the exchange or business activities of the SWX Group. Le présent e-mail est un message privé et personnel, sans rapport avec l'activité boursière du Groupe SWX. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. --------------------------------------------------------------------- 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
|