Upgraded to Mac OSX Tiger and now apachectl -startssl no longer needed
Mark Leone <[email protected]>
| Newsgroups | gmane.comp.apache.mod-ssl.user |
|---|---|
| Message-ID | <[email protected]> |
I finally got around to upgrading my Mac to Tiger. I had to copy my old httpd.conf file to the proper directory; but other than that it works fine. However, apachectl no longer accepts "startssl" as an argument (it returns with a "usage" instruction that prescribes start, stop, etc.). It works fine with "apachectl start"; but to my surprise the server that starts up with this command accepts https requests and sends the cert I set up previously. I could re-build and re-install apache and mod_ssl as I did originally before the OS upgrade, but do I need to bother with that? I remember that apachectl should require startssl as an argument in order to startup the SSL server, so it seems something weird is going on, and I wonder if I need to make it behave the way it used to. -Mark ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [email protected] Automated List Manager [email protected]