On 05 October 2001, Mikhail Sobolev said:
> I just downloaded Quixote v0.4 and tried to install it on my computer.
> System:
>     Win2k (SP2 if it matters)
>     IIS (5.0)
>     Python 2.1

Ahh, good.  This is the first I've heard of someone trying Quixote on a
non-Unix, non-Apache platform.  I'm not surprised there are problems,
but I'm optimistic that we can take care of them.

> I tried to run the demo script (installed quixote and placed the
> demo.cgi file as demo.py in my scripts directory) and run it.  The first
> attempt failed as I did not fullfil the requirements (did not install
> the compiler), but after that I keep getting 404 error.  I activated
> the access log (in demo.conf) and made sure that my request is
> registered there.  Here is the line:
>
> 127.0.0.1 - 2001-10-05 13:28:22 1976 "GET None HTTP/1.1" 404 0.00sec
                                            ^^^^
Oops: that just means we're using an Apache-specific environment
variable for logging (REQUEST_URI, which isn't in the CGI spec).  I'm
pretty sure that's not the problem, but I'll attach a patch for it
anyways.  Please let us know if it works -- this should improve
portability to non-Apache servers.

The real problem here seems to be that Quixote's traversal algorithm is
falling down.  Obviously, you're getting into Quixote, or you would't
see that line in the Quixote access log.  So CGI execution works.

I wonder if the IIS environment is missing more stuff that Quixote
relies upon?  I'll attach a standalone CGI script that you can run; this
just dumps the complete request (stdin, environment, command-line) into
the output web page.  Install this on your system and access
  http://localhost/scripts/dumpreq.py
and tell us what you get.  (The environment variables are most important
-- you should just copy and paste the list from your browser to
email.)

> The URL I used was:
>
>     http://localhost/scripts/demo.py/

That's almost certainly correct, otherwise Quixote wouldn't have updated
its access log.  Just for grins, try accessing
    http://localhost/scripts/demo.py/simple
    http://localhost/scripts/demo.py/error
    http://localhost/scripts/demo.py/foobar
*after* applying my logging-patch, and see what shows up in the access
log.  You should also configure Quixote debug and error logs and check
them, and also check IIS' error log.

        Greg
--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org