Matus \"fantomas\" Uhlar wrote: > > Hello, > > I'd like to know, how does modssl decide which port is ssl and which one is > non-ssl? if I bind apache to two ports, how to tell which one should be used > for ssl connects and which one for non-ssl connects?
Apache is the process - mod_ssl is just a module. Only port 80 is listened to by default by apache so to get SSL to work you must explicitly say "Listen 443". > > Another question. if I run http on port 80 and httpd on port 443, and I > define only one virtualhost: > > <VirtualHost ip.address> > ServerName blablabla > </VirtualHost> > > will that virtualhost be available via both ports/protocols? I guess so... but this not a good idea since SSL requires lots of extra directives (like "SSLEngine on" - how they would interact with the HTTP host is not obvious... > Or, do I need to define two virtualhosts, one on port 80 without ssl and one > on 443 with ssl? This is a much better idea - keep the SSL and HTTP hosts completely separate, you will sleep better. > Warning: I don't wish to receive spam to this address. You'll be lucky! ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
