If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

IIS vs Apache vs Others

02-19-2015, 11:55 AM

I know there are a lot of followers of both sides, a lot of people hates IIS, but I Would like to know your opinion. Pros and cons about each one. Always used Apache but I readed good reviews about latests IIS versions.

The major disadvantage of IIS is that on each and every new version the security settings change, causing a real maze of options where you get lost if you want to achieve some simple things like allowing to install a webservice, or setting rights for directories. If you run plesk then these issues are minor because with plesk you can do all the necessary settings pretty easy. So currently I'm running Scriptcase production on an IIS system and no issues at all, except that I need to change rights before defining the connection which I need to roll back afterwards (something similar with 777->644). Again, with plesk maintenance of the server is easy.
But if you are running a server with plain iis then it's a complete nightmare imho.

I still like apache the most, there are great packages like uniform server, completely packaged for production. Loads and loads of support forums and docs to find your way.

Comment

IIS easy in administration? Well I dare to say it isnt that easy. Under apache you can get a really fine administration via config files on iis you need to know where the settigns are. If you are not used to it then you really need to do some digging on occasions. Yet if the applications are pretty stanadard then it is fairly easy. Without plesk it is harder to find out every detail. Although you can seriously have a lot of settings in IIS, some controllable via scripts.
One interesting difference is the timeout, say someone goes to http://myserver/nonexistingpage.dll then IIS will always respond with a timeout result page if the dll doesnt respond quick enough. Apache on the other hand doesnt respond to the client properly and the browser gets a timeout.