“Whether you’re an administrator or a developer, you must understand what’s in store for you when you start using Internet Information Services (IIS) 6.0, which ships as part of the Windows .NET Server product line. The key interests of developers and administrators alike include security, stability, scalability, and programmability. Here’s how IIS addresses those needs”. Read the interesting review at .NETMag, while you can also similar explore interesting articles like “Evaluate Windows .NET Server” and “Internet Information Services 6.0 Overview – Beta 3″.
IIS will never be secure, or, I should say, as secure as Apache. I don’t care what they say, I will never trust it again
“IIS” and “security” in the same paragraph no less. No, this isn’t the latest advisory from eeye, so what business do these words have being anywhere near each other?
Please, spare me the 4am pages and frantic calls from management. I’ll believe it when I see it… until it’s proven, its all rhetoric and vapourware.
Well for one, when you install it, the first time you run it, it comes up with a wizard asking what parts of IIS you need, and everything else is left disabled.
Second, IIS6 has a lot of re-written stuff.
Third, IIS is perfectly fine if you stay up to date on the patches.
Yeah for the firewall (also WinNT based
[ Personally I’d use Tomcat, but hey thats just me ]
Well for one, when you install it, the first time you run it, it comes up with a wizard asking what parts of IIS you need, and everything else is left disabled.
Well, that’s great. Nice to see they finally got to that point, its only taken them til version 6 to figure out what most level headed developers knew a long time ago.
Second, IIS6 has a lot of re-written stuff.
Since when does new code = better code?
Third, IIS is perfectly fine if you stay up to date on the patches
Have you ever had to actually maintain a large number of IIS servers before? I, for one, have better things to do than spend my time patching buggy software when a far better alternative exists, for a fraction the cost. Now, doesn’t that seem like a sound business judgement?
Archeron: Far better? You just can’t say that, IIS offers many features which are not available in Apache.
I didn’t say new code, I said re-written code. They re-thought out the code, in other words.
I assumed you maintain 150 MS IIS servers just the same way you maintain 150 RH Workgroup Apache boxes…
Run the GUI updater on the test system, accept critical security updates, let it run under load for a while, check you don’t see any regressions then select the 150 live servers and click “schedule next update, critical updates”
If it’s harder than that then I guess I have to once again count myself lucky that I’m not struggling with “easy-to-use” Windows.
Archeron: Far better? You just can’t say that, IIS offers many features which are not available in Apache.
I don’t think it having more bugs, *koff* I mean features, makes it better than Apache. Personally I feel that any software that has that security record, that price and that amount of service packs needs avoiding.
sounds strikingly similar to the questions asked buy sum of j. gotti’s hostages in the garmeNT disstricked, a while back.
how much does IT cost? NO m$ apologist/oss basher, EVER even attempts to begin to answer that won.
see also: <a href=http://www.trustworthycomputing.com>innovation?
ms_b0b, or ms_bob, whatever … you *might* get taken a little bit more seriously if you tried spelling things correctly. Heck, even getting in the ballpark might help you some.
That, and possibly making sense. Of course, that might be asking a bit much.
Why should customers keep up with patchs if Microsoft doesn’t? I don’t know if you all know or not that M$’s site was defaced for the 4th time this month last sunday because they didn’t patch their IIS server even though they released the fix for that hole the hacker group used about a week before it happend. Microsoft also says that it’s the IIS users’ fault for code red’s damage because the admins didn’t stay up-to-date with patchs. Now it seems to me that Microsoft has no room to talk.
By the way CPUGuy, IIS has no real features worth using in the first place, and how can those be IIS features since they’re basically ‘span-in’ modules. Apache has a lot of built-in features and Apache with modules makes it even better because the modules that come with Apache RPMs are very useful! Can we say the same for IIS? Nope. IIS is not worth it, and it shows that apache owns all over web servers because it’s the most widely used and popular web server out there, over 60% of the web is being ran on an Apache!
I think people should take a look at http://www3.gartner.com/DisplayDocument?doc_cd=101034“>this . Gartner have usually been very pro-Microsoft, so I think that lends even more weight to their claims here.
mod_perl
php
they work great on apache…
and php has more feature and additional stuff (like gtk_php)
than similar server side languages
Apache is a far more better webserver, and it takes less resources as a mem hogging IIS server. It’s a fact that apache hosts more sites on a single machine then iis can. So i really don’t know people are choicing for IIS. Is it cheaper, easier , it has nimda (something other server don’t have), more stable? I dunno…
And yes this auto update sounds kewl, but hell how often MS releases patches which needs to fix the previous patch! I saw like 2-3 box which needed a re-install after a patch install!
So yes this feature is kewl.
To my Apache fans, let’s wait on Apache 2.0
ASP. Simple. It allows many programmers to write web page applications in an easy-to-use programming language (VBScript). It also integrates nicely with SQL Server.
If it weren’t for ASP (.NET too) I think IIS would have bit the dust a while ago.
I program both ASP and PHP, and by far and away prefer PHP. The sheer number of incredibly convenient functions available is enough, but there’s more. The smooth SMTP interface and MySQL interface are great.