Seems like a very simple, lightweight and elegant solution to keeping the engine up to modern standards. If they were serious about keeping complexity out they wouldn’t have such garbage site configuration.
Some of my static sites are definitely not configured correctly and show the default error messages. A lot of sites have dynamic content though, and are often configured like:
try_files $uri $uri/ @backend;
So any requests for files that don’t exist get routed to the backend, which usually shows its own error messages instead of Nginx’s.
As if I needed another reason to avoid nginx.
Seems like a very simple, lightweight and elegant solution to keeping the engine up to modern standards. If they were serious about keeping complexity out they wouldn’t have such garbage site configuration.
Really, this minor issue you’ll never run into is a reason to avond nginx
It’s the little things that always add up. It’s not the lack of feature but their dismissal of it I guess.
Most server admins use custom 404 pages, so the default page isn’t that common in production.
And yet everyone has stumbled into them a few times.
Some of my static sites are definitely not configured correctly and show the default error messages. A lot of sites have dynamic content though, and are often configured like:
So any requests for files that don’t exist get routed to the backend, which usually shows its own error messages instead of Nginx’s.
Good to know. My experience with nginx is definitely on the light end. I much prefer traefik I guess coming from k3s world.
I only really knew of Apache as an alternative before.