3 ms·
I'm surprised by the lack of first-class ACME/Let's Encrypt support. I figured once Caddy paved the way in that regard that nginx wouldn't be far behind.
by Zikes 9y ago
I'm surprised by the lack of first-class ACME/Let's Encrypt support. I figured once Caddy paved the way in that regard that nginx wouldn't be far behind.
- jxi 9y agoThanks for the reference to Caddy! Looks like a pretty neat project. I'm also bummed by nginx's lack of end-to-end HTTP/2 support.
- lprd 9y agoI was just thinking the same thing. I've been using Caddy for about a year now and love it.
- pfg 9y agoI'm all for adding native ACME support to web servers, but I can understand that they'd rather wait till ACME reaches RFC status (which hopefully won't be long now - the draft is in WG Last-Call). Once that's done, I'd definitely be disappointed if web servers still decide it's not in scope for their core product.
- Zikes 9y agoI don't think it's unreasonable to expect an officially supported optional module, at the very least. It's how they've handled experimental features in the past.
- _mikz 9y agoThere is lua-resty-auto-ssl [1] providing exactly that. Sure, it is not plain Nginx, but OpenResty. [1] https://github.com/GUI/lua-resty-auto-ssl https://github.com/GUI/lua-resty-auto-ssl