On Wed, Aug 09, 2000 at 10:06:00AM +0200, Owen Boyle wrote:
...
The recommended solution is to use a different IP address for the SSL
virtual host. This would obviously solve the problem since the server
can go immediately to the SSL VirtualHost as soon as it receives a
request on that IP
However, the problem is that (as I understand it):
- the GET request for the SSL page comes in already encrypted (the
browser knows to encrypt it because the URL begins with "https").
- The server tries to do virtual host resolution first so tries to find
the ServerName in the request.
The following is an !excellent! clarification of the mod_ssl FAQ re use
of NBVH for SSL. If some of this were added to the FAQ it would
eliminate a fair number of posts to this list ;)
Thanks Dana!
James Moore
On 9 Aug 00, Dana Powers wrote:
snip
What happens is the client browser sees
