It is not as yet clear if "IIS 5 compatibility isolation mode" is needed or all that is needed. The user experience seems to be all over the map. We're working on it...
Folks run IIS for a variety of reasons, many of which make sense. NTLM authentication is one - the mod_auth_sspi module used in Apache is bound to be least a step behind the builtin code used by IIS. There are all sorts of quirks with differing versions and setups (which have caused us grief) that make delegating NTLM to IIS a win. In terms of performance and reliability, there really are not significant differences between Apache (the HTTP server) and IIS anymore. Lots of folks are running old ASP and new .NET applications as well, and using IIS is less trouble than using Apache. All good reasons... Upshot is, there is value in a way to cleanly plug in one or more server-side Java applications (possibily running on different machines) behind a single IIS server. (ack - runon sentence). On 12/13/05, Jess Holle <[EMAIL PROTECTED]> wrote: > > In IIS 6, you also have to run in IIS 5 compatibility isolation mode. > > I have no love for IIS myself but we also have customers that have some > inexplicable emotional attachment to it. Is it just NTLM? In which > case someone should shove mod_auth_sspi into Apache and be done. If > not, what's the fascination with IIS? In our case our application is > purely Java, so in direct conjunction with it ASP, .Net, etc, are of no > benefit whatsoever. > > It would be helpful if either: (1) all remaining rational reasons for > using IIS (e.g. NTLM) were answered by Apache or (2) the IIS/Tomcat > connector was not the ugly step child that no one wanted. >
