Further work on this problem: I removed the existing apache22
installation which pkg_add had created (in /usr/pkg), set up pksrc, and
built another apache 2.2.8 (httpd) from source. This one has mod_ssl in
it, but it complains only slightly about missing ssl stuff.
Results are the same, kind
I just realized that I didn't answer all of your questions:
The NetBSD computer on which this apache is installed is part of my home
LAN, so I'm not running a browser on the machine running the server: I'm
running the browser on a laptop in the other room.
Regards,
Frank H.
William A. Rowe,
Greetings,
I'm running NetBSD 4.0. I used pkg_add to install apache-2.2.8, but
had mod_ssl.c compiled in and wanted that to start. I would rather not
deal with SSL just now: I don't need it, so I downloaded the source,
configured a different httpd and put it in /usr/local (pkg_add had put
Frank Huddleston wrote:
Greetings,
I'm running NetBSD 4.0. I used pkg_add to install apache-2.2.8, but had
mod_ssl.c compiled in and wanted that to start. I would rather not deal
with SSL just now: I don't need it, so I downloaded the source,
configured a different httpd and put it in
OK: I added those directives: results look unchanged.
Result of the apr-1-config command:
$ apr-1-config --version
1.2.9
I also noted that, using the Safari browser instead of FireFox, the URL
of the image file is not displayed: nothing is displayed.
Also, I have fancy directory listing
Is it possible that the web server is speaking HTTPS and the web browser is
speaking HTTP?
Cheers
--
Lloyd Parkes
Senior Systems Programmer
Open Systems
Ph: +64 4 890 2437
-
The official User-To-User support forum of the
Well, the messages that the server sends, such as status messages, error
messages, and the headers for the directory listings, all come out OK.
Wouldn't everything be encrypted if it were speaking https?
There's this at the bottom of the httpd.conf file, but as I don't have
mod_ssl compiled in,
