this post was submitted on 03 Apr 2024
94 points (92.0% liked)
Technology
59137 readers
2267 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Nginx also increased in popularity around that time, giving more competition to IIS. Most of the web stacks I've seen recently are running Nginx.
(I'm an HAProxy man myself.)
NGINX is rarely used as a web server, it's usually used as a reverse proxy, cache and SSL terminator. Just like HAProxy, Varnish, etc.
How are we defining a web server? Because to me it's "the thing listening on Port 80 or 443 that responds to HTTP requests."
And, yes, I know they do more than that, but they also do those things quite a bit.
There's a pretty clear distinction between a web server and a reverse proxy if you work in the field.
I've got over 20 years of experience in the field. I've configured both of them as reverse proxies and web servers.
If Nginx is accepting connections on ports 80 and 443, terminating SSL, and responding to HTTP requests, that makes it a web server. Especially if it's responding with static content.
Oh my...