On Thu, 2018-11-15 at 09:27 -0500, Olaf van der Spek wrote:
> Jim Popovitch Wrote:
> -------------------------------------------------------
> > On Thu, 2018-11-15 at 08:36 -0500, Olaf van der Spek wrote:
> > So a specific use case.  What about port 443 (you haven't mentioned
> > it
>
> What about it?
>
> > yet), except what if it's on a non-routable subnet perhaps 8443
> > should
> > be preferred then?  
>
> Why? 
>
> > Should nginx also look for certs in /etc/ssl/ that
> > have file names that align with server_name?  What about multi-homed
>
> I had thought about that.. maybe but that'd be another feature
> request.
>
> > servers, should the listen directive default to the IP address(es)
> > that map to server_name?  
>
> No
>

Heh, those weren't really questions necessitating answers from you. I
apologize if they appeared to you as such.

On a side note, github suggests that we share a common interest in C&C.

Best wishes,

-Jim P.


_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx