5 ms·
lighttpd is hardly comparable to nginx. For example, it still lacks http2 support.
by xeeeeeeeeeeenu 8y ago
lighttpd is hardly comparable to nginx. For example, it still lacks http2 support.
- yjftsjthsd-h 8y agoDepends what you're doing. If you just want "http server" of some kind, then either is fine. Sure, features vary, but how much does it actually matter? Yeah, http2 is nice, newer compression is good, ... features matter, but for a lot of uses it really doesn't make a noticeable impact.
- msbarnett 8y agoIf you just want a bare bones http server of any kind, nginx is probably overkill in the first place.
- majewsky 8y agoI would argue the opposite: Anything but nginx is probably overkill unless you have specific requirements. I mean, sure, if you just want to serve some files from a development machine into the intranet right now, `python -m http.server` will do the trick. But for anything that is either a productive system, or one serving content to the public internet, nginx is a sane default choice.
- msbarnett 8y agoFor a production system facing the public, lightttpd strikes me as inappropriate. Any of the “I don’t care how poorly it supports modern browsers, I just need something barebones that speaks http” usecases the person I was responding to seemed to be suggesting would typically be something like a local dev http server, or a barebones http server sitting behind a more robust proxy. Which brings us back to, for those usecases, nginx is probably overkill.
- _0ffh 8y agoYou mean that unnecessarily complex successor of http1.1 that brings nothing to the table you'd ever need if your website wasn't a bloated piece of </censored>?
- ksec 8y agoTry H2O [1] [1] https://h2o.examp1e.net https://h2o.examp1e.net