NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Problem with httpd and openssl on NetBSD-7.1



Gary Duzan <gary%duzan.org@localhost> wrote:

> In Message <10926.1493743900%secondfloor.xyz@localhost>,
>    Christopher Pinon <cjpinon%secondfloor.xyz@localhost>wrote:
> 
> =>J. Lewis Muir <jlmuir%imca-cat.org@localhost> wrote:
> =>
> =>> On 05/02, Christopher Pinon wrote:
> =>> > By the way, another (easier) question about httpd: is there a way for
> =>> > httpd to listen to both plain http (port 80) requests and https (port
> =>> > 443) requests? (Like apache.) At the moment, as far as I can tell, it's
> =>> > either or, depending on whether or not '-Z ...' is set.
> =>> 
> =>> I've not tried, but can't you just run two instances of it: one
> =>> listening on port 80 and the other listening on port 443?
> =>
> =>Thanks, Lewis: indeed, this works. :-) I guess that I was focused on
> =>doing this from /etc/rc.conf, but for no good reason, really. Am
> =>beginning to warm up to httpd after a long time with apache!
> 
>    You still can use rc.conf, if you'd like. Copy /etc/rc.d/httpd
> to /etc/rc.d/httpsd (or something like that), and tweak the copy
> to have a different name, rcvar, and command_args. Then you can
> specify httpsd=YES in /etc/rc.conf, along with other variables you
> need for command_args.

Thanks, Gary, good point, that would surely work.

I guess that I was instinctively looking for a more minimalist solution,
and what seems to work is that I start one instance (in my case, the
SSL-instance) of httpd in /etc/rc.conf (as I was doing) and the other
(non-SSL) instance is handled by inetd (I had to modify /etc/inetd.conf
for this). This has the minor advantage (in addition to less
configuring!) that the non-SSL instance of httpd is only started when
needed. It seems to work. :-)

C.


Home | Main Index | Thread Index | Old Index