static-server: an HTTP server in Go for static content

Re:static-server: an HTTP server in Go for static content by mholt on Saturday September 16, 2023 @06:34PM (#37539473)

Caddy 1 was created because I needed a quick and easy web server for a lot of my projects.

Caddy 2 was created when I got serious about it, and we had governments and enterprises starting to rely on the project.

Now we exist because we advocate for (and deliver!) HTTPS on every site, memory safety, dynamic configuration, extensibility, and many more features valuable in a modern web server.

Hope that helps :)

[ Parent | on HN ]

Re:static-server: an HTTP server in Go for static content by abhishekjha on Sunday September 17, 2023 @12:24AM (#37541512)

Thank you for the response. It looks interesting.

>I needed a quick and easy web server

I am trying to reason with what I know, but wouldn't something like "python -m http.server 9000" suffice? Or nginx? These are battle tested and python is there on most platforms.

Or is there more depth to this specific web server that others don't have?

[ Parent | on HN ]

Re:static-server: an HTTP server in Go for static content by mholt on Sunday September 17, 2023 @01:18AM (#37541762)

No, because python's simple HTTP server isn't production ready (doesn't support Range requests last I checked, and quite a few other limitations). And nginx is not "quick and easy" by any means, doesn't grant me the security of memory safety (it was vulnerable to Heartbleed, for example -- I wrote Caddy shortly after Heartbleed), and doesn't give me automatic HTTPS.

And Caddy is very well battle-tested too, btw. ;)

[ Parent | on HN ]