Connecting IIS to Zope, the relatively clean and relatively fast way

Tired of ugly URLs and slow PCGI performance? Longing for a solution that doesn't spawn another process for each hit? Envious of your friends that have it easy just because they can run Apache in front of Zope while you're stuck with IIS?

This is a rewrite of Andy McKay's error.asp script

This script forwards IIS requests to Zope much like ProxyPass does for Apache, using Virtual Host Monster to generate correct dynamic URLs. You just need to setup IIS to handle 404/405 (Not Found) errors with it.

Main differences to Andy's script include:

• New COM object ("WinHttp.WinHttpRequest.5.1") which fixes the caching and redirect problems mentioned by Andy.
• Easier configuration. Just two very obvious configuration variables in the beginning of the script. No more fiddling with Virtual Host Monster URLs. We generate them all for you.

Issues:

• No streaming pages. IIS collects the Zope response before sending it to the Browser, so "RESPONSE.write()" based pages will return only when finished. But don't worry about it if you don't know what "RESPONSE.write()" is.
• It's in ASP (VBScript), so it will never be as fast as a proper connector writen in C/C++, but it's still at least twice as fast as PCGI (according to some vague anedoctal measurements, so don't take our word for it).

Dependencies:

• Windows 2000 or XP (NT4 no longer supported, but still possible. Read the Script).
• IIS

We are currently running this Script in Production.

Read the Script itself for installation and configuration instructions.