On 08/06/2010 2:08 PM, Adkins, Marc wrote:
You can't serve HTTP and HTTPS content from the same vhost.
Where is that documented? I've been reading various documents for a
while without running across that caveat. Though it makes some sense
in retrospect.
You can use the Include directive to reduce clutter.
Yeah, that's what I was thinking. Just thought there might be a magic cookie.
---------------------------------------------------------------------
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-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
---------------------------------------------------------------------
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-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Marc,
The "SSLEngine on" line will not be valid in a HTTP vhost (*:80), since
the HTTP client will not expect a SSL handshake. Clients will respond
differently to that scenario, but in any case, a warning will be displayed.
Surely, you want to present that to your customers.
Frank.
---------------------------------------------------------------------
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-unsubscr...@httpd.apache.org
" from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
