durusmail: quixote-users: Serving quixote through iis
Serving quixote through iis
2005-10-06
Serving quixote through iis (while fixing a Quixote-WSGI bug)
Re: R: [Quixote-users] Serving quixote through iis (while fixing a Quixote-WSGI bug)
2005-10-06
2005-10-06
2005-10-06
2005-10-06
2005-10-07
Re: R: [Quixote-users] Serving quixote through iis
2005-10-07
Re: R: [Quixote-users] Serving quixote through iis
2005-10-07
Serving quixote through iis
Patrik Simons
2005-10-07
On Thu, 6 Oct 2005 11:43:52 +0200 "Daniele Varrazzo" 
wrote:
> Is there any chance to make iis run an application through many requests?
Maybe the simplest thing would be running quixote through Medusa on a private
port and letting iis forward it the related request. Is it possible?
>
> Did anybody face the same problem and has some tip to share, or some scar to
show, about that?

Scar indeed.

I have used SCGI-CGI (http://arbutus.physics.mcmaster.ca/dmc/software/)
together with a python scgi server installed as a service.
However, SCGI-CGI needs heavy patching to compile under mingw32 and
IIS has some annoying CGI bugs.

For example, if the status code of the http response is anything but
200, then IIS 5 will replace the response with its own. IIS 6, on the
other hand, also replaces the response but doesn't touch the
content-length header, leaving your browser waiting for data that won't
arrive if your response happens to be longer than the IIS default one.

The workaround is to strip away the content-length header before
passing the response to IIS. This way your redirects will work
again. You'll have to use status code 200 for all the other error
pages. Also note http://support.microsoft.com/kb/q176113/

Lately, I've been using an isapi extension instead. This lets me access
all the IIS specific server variables as environment variables in the
request. See http://www.neotide.fi/quixote/

--
Patrik
reply