2 ms·
It actually is sort of both. The core feature set is well designed and relatively slim, and supports the three most common topologies - as a front end for stati
by TylerE 15y ago
It actually is sort of both. The core feature set is well designed and relatively slim, and supports the three most common topologies - as a front end for static content, as a front-end up for an external "web engine", e.g. php-fpm or rack or a WSGI app, or as a reverse proxy/load balancer.
It's a very good 90% solution - 90% of the time it does everything you need, and it does it well. That comes at the cost of supporting certain corner cases or features, WebDAV for instance.
Where it might not be as good as in something like a shared hosting environment where you want to give users something they can tweak like an .htaccess file. That sort of per-request configuration loading runs counter to the performance profile they're trying to provide.