Dude, I learned how to write HTML in the 90’s and even back then everyone knew that apache2 was clearly fucking superior. IIS has been a joke since the 90’s when it was released.
Maybe I’m wrong, as I only tried to get it up and running once back around 2000’s, but it seemed like IIS had like, no configuration options? Like you set it up, and that’s it. What if I want to do something other than what Microsoft intended? Always struck me as odd for a web server.
But, exactly as you’re saying, lol I tried it once, it sucked and I went to apache instead
Except that’s not what was happening. IIS came after Apache and played a catch up for a while. It almost surpassed Apache in 2007, but GFC happened and its popularity dropped rapidly. If not for GFC, there would be no Apache today.
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.
Dude, I learned how to write HTML in the 90’s and even back then everyone knew that apache2 was clearly fucking superior. IIS has been a joke since the 90’s when it was released.
Maybe I’m wrong, as I only tried to get it up and running once back around 2000’s, but it seemed like IIS had like, no configuration options? Like you set it up, and that’s it. What if I want to do something other than what Microsoft intended? Always struck me as odd for a web server.
But, exactly as you’re saying, lol I tried it once, it sucked and I went to apache instead
I remember trying to get it to work with MySQL, failing, and moving to apache.
Except that’s not what was happening. IIS came after Apache and played a catch up for a while. It almost surpassed Apache in 2007, but GFC happened and its popularity dropped rapidly. If not for GFC, there would be no Apache today.
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.