-> > -> > 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". -> > -> > Yes i know that :) The question is - how will mod_ssl know that it -> > should process connections on port 443 and not on port 80. -> -> For one, it's a standard well known port: -> -> darkstar:~# grep 443 /etc/services -> https 443/tcp https # http protocol over -> TLS/SSL
Does mod_ssl walk through /etc/services ? By compile time or by runtime? -> for two, it would most likely be part of your httpd.conf, with the listen -> directive. How do I define that apache should accept only non-encrypted connections on port 80 and only encrypted on 443? What if I would use other two ports? 81 and 444 for example. Would apache crash? or will it tell it doesn't know what kind of connections should wait on those ports? or will it expect http connections everywhere? -> > hmmm. I think I can put genric SSL directives into server's config and -> > none special are _required_ for virtualhosts. I just have some -> > virtualhosts and wish to give access to all of them without -> > reconfiguring them. And that ebout sslengine was exactly hat i -> > wanteddo know. couls i turnon SSLEngine on for all connections to one -> > port and turn it off for all connections on other port? -> -> Have you actually parsed through the defult httpd.conf file that is -> installed when you compile the openssl/mod-ssl/apache combo <some folks -> will ass in MM in that combo> It's pretty well documented, and reading -> through it as one parses the FAQ and other documentation included is -> always a good starting point. I didn't install anything yet. I am deciding between apache-ssl and mod-ssl; I did search the docs on the web. But i could not find answer to my questions. That's why I subscribed here. Maybe you could point me to exact answer of my question; <VirtualHost 192.168.0.1> ServerName blabla1 </VirtualHost> <VirtualHost 192.168.0.1> ServerName blabla2 </VirtualHost> will both servers, blabla1 and blabla2 be available on port 80 w/o SSL and on port 443 with SSL? should I use this to define behaviour of ports? <VirtualHost *:80> SSLEngine Off </VirtualHost> <VirtualHost *:443> SSLEngine On </VirtualHost> -- Matus "fantomas" Uhlar, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I don't wish to receive spam to this address. Varovanie: Nezelam si na tuto adresu dostavat akukolvek reklamnu postu. I drive way too fast to worry about cholesterol. ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
