-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ksenia Marasanova wrote:
|> Hi Ksenia,
|>
|> I'm relatively new to Quixote/mod_scgi myself, but I had a similar
|> problem; in my case, it was related to settings in demo_scgi.py. In
|> DemoHandler, root_namespace should be set to ``quixote.demo'', and
|> prefix should be set to the location of the demo script relative to your
|> DocumentRoot. So in my case, Quixote is installed as a Python module,
|> mod_scgi is configured to use port 4000, DocumentRoot is set to
|> /var/www/localhost, and the Quixote demo lives in
|> /var/www/localhost/demo, so in DemoHandler in demo_scgi.py, prefix =
|> "/demo". The demo is started with demo_scgi.sh, and if you nmap
|> localhost, you should see something on port 4000 (or whichever one your
|> Apache/mod_scgi is configured to use).
|> BTW, I'm running Gentoo/Apache 2.0.48
|>
|> HTH,
|>
|> Uspehov,
|>
|> Renat
|>
|
| Renat,
|
| Thank you!!!!!! You've just gave me an extra view hours of night sleep.
| What a stupid mistake of me - i did not modified demo_scgi.py, but I
| used my own Location directive:  instead of .
|
| Spasibo! (let's not forget this great language, right? ;-)

So Ksenia's issue has been resolved (except that I forgot to cc the list
and replied directly to her).

| P.S. Okay... there is another problem. If the page is refreshed first
| time, there is error 500 - error reading response headers. After
| refreshing it second time, everithing works normal. Refresh - error.
| Refresh - okay. Strange, isn't it?

I get the same behavior here. I don't know enough about the inner
workings of Quixote to understand why it's happening. Maybe the powers
that be will help?

Best,
- -- Renat
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFASowYEzitwsaoONoRAiJ6AJ9YB2Kdk+B7GCOCRrsGgxIemcCM9wCfdlW7
r2hiAwgzsi9eOwyMX+rQjW0=
=KeoP
-----END PGP SIGNATURE-----