On Mon, Jun 19, 2000 at 10:00:43PM -0400, Michael J. McGillick wrote:
> Evening:
>
> I just installed the latest apache-1.3.2 and mod_ssl-2.6.4-1.3.12
> patch. I have a couple of questions to ask:
>
> I started up the server by just typing:
>
> /usr/bin/httpsd
>
> Is this correct, or is there another mechanism I should be using?
>
> Next, I went to a browser on another machine, and pointed it at my machine
> running apache. If I type in http://<URL>, the page comes up just
> fine. If I type https://<URL>, I get a message that the page can't be
> found. I'm running with the default httpsd.conf file that gets installed,
> and I did a tail -f on /var/log/httpsd/httpsd_error.log while
> connecting. No errors showed up. Am I missing something or doing
> something wrong?
You should start the server with the command:
/path/to/apache/bin/httpd -DSSL
or use
/path/to/apache/bin/apachectl startssl
>
> I've heard mention of modules. I'm not 100% sure exactly what these
> are. Is there a good document that covers what they are, and how to go
> about adding them so apache can use them?
http://www.apache.org/docs/ would be a good starting point.
> Are they something that can be
> added to the apache build process, or do they get added in after by
> separate compiling?
>
You can do both. If you want to add modules later, then Apache should
originally be compiled with DSO support (mod_so). The Apache+mod_ssl
INSTALL document has the configuration directives for DSO listed among
the optional configuration directives.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
