> Neil Schemenauer wrote:
> If you replace "qdemo" with "site" that should just work.  It would
> be helpful if you could figure out if the request was getting passed
> to the scgi server or if Apache was the one returning the "page not
> found" error.
>
> You can also get Quixote out of the picture by using the simple SCGI
> echo server that is part of scgi_server.py.  Just run:
>
>     python scgi_server.py 
>
> and then test from your browser.  If you get a response back (it
> should be a plain text dump of the request) then the Apache
> configuration is okay.  If you don't then probably the problem lies
> with the Apache config.

Thanks for the quick reply; just got around to further testing this
afternoon, and tried the above suggestion first.

I found that the Apache and scgi config was fine, and that the problem must
lie elsewhere in my code itself. Maybe I missed replacing "qdemo" somewhere?
But things looked right until I realized that that "site" corresponded to
the standard Python site module! I changed everything to "main" and it ran
as expected. Sigh...

I think I'm going to stick to "main" for my site, but as an academic
exercise, how would I avoid such a problem in the future?

Regards,

Robert M. Anderson
Technical Publication Section
Nikko Graphic Arts Co., Ltd.
Shizuoka, Japan