> > Yes, I can see the need for a separate port, but it's not clear why VH's > are/must be used to separate off the HTTPS activity on port 443. > > As I mentioned on my last reply, I'm hoping that http://myserver and > https://myserver both work; the first on :80 and the 2nd on :443. Am I > expecting too much? Is this unpossible? > Specifying http:// will cause the browser to use port 80 by default. Specifying https:// will cause the browser to use port 443 by default. However, apache does not automatically assume that 80 == http and 443 == https, you need to use the SSLEngine directive to turn it on for a particular port. This is done by creating an IP/port based virtualhost (as opposed to name based virtualhost) so that you can turn on SSLEngine for port 443 but not for port 80 - hence the need for the virtualhost. Regards, Paul --------------------------------------------------------------------- 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
|