Welcome! Log In Create A New Profile

Advanced

Re: Enable http2 and ssl by default

November 15, 2018 09:27AM
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
Subject Author Posted

Enable http2 and ssl by default

Olaf van der Spek November 14, 2018 10:40AM

Re: Enable http2 and ssl by default

Jim Popovitch November 14, 2018 12:46PM

Re: Enable http2 and ssl by default

Olaf van der Spek November 15, 2018 08:05AM

Re: Enable http2 and ssl by default

Jim Popovitch November 15, 2018 08:18AM

Re: Enable http2 and ssl by default

Olaf van der Spek November 15, 2018 08:36AM

Re: Enable http2 and ssl by default

Jim Popovitch November 15, 2018 09:04AM

Re: Enable http2 and ssl by default

Olaf van der Spek November 15, 2018 09:27AM

Re: Enable http2 and ssl by default

Jim Popovitch November 15, 2018 10:42AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 75
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready