News for hackers. Stuff that matters.
Re:Caddy Server Is Acquired By Apilayer by mholt on Thursday September 10, 2020 @04:20PM (#24436180)
> Has there been any memory safety issues with Nginx?

Yes, of course. For example, nginx uses openssl, so it was vulnerable to Heartbleed, something Caddy can never be vulnerable to. Part of the point of Caddy is to stop deploying C code to the edge.

> Nginx is easily extendable and has far, far larger plugin ecosystem than Caddy.

Nginx is also 4x older. I'd say for just a few years we're doing pretty good with our very young plugin ecosystem. A lot of this depends on the community. If you want it, make it so!

> So does nginx, with "nginx -s reload"

I think he was referring to a REST/JSON API that isn't unix-specific.

Re:Caddy Server Is Acquired By Apilayer by calcifer on Thursday September 10, 2020 @05:06PM (#24436564)
Good point about openssl!

> Nginx is also 4x older.

I know, but the GP claimed Caddy's plugin ecosystem was an advantage over Nginx, which just isn't true.

> I think he was referring to a REST/JSON API that isn't unix-specific.

Got it, thanks. Though I wonder how many people actually need a REST API for config reloads given practically everyone runs servers on Linux.

Re:Caddy Server Is Acquired By Apilayer by joshmanders on Thursday September 10, 2020 @08:32PM (#24438048)
You'd be surprised how helpful having a REST API for config reloads is when you're serving more than a simple static site.