Neil Schemenauer wrote:

>On Mon, Apr 25, 2005 at 04:10:05PM -0700, mso@oz.net wrote:
>
>
>>Why is mod_scgi unable to do this?  Does Apache not have the
>>information ready when mod_scgi executes?
>>
>>
>
>No, I don't think it does.  The problem is that Apache does not know
>what the SCRIPT_NAME part of the path should be.  We could just say
>the path of the Location directive is the SCRIPT_NAME.  One problem
>is that using Location is only one way to use mod_scgi (you could
>use mod_rewrite to set the handler, for example).
>
>The current development version of mod_scgi passes environment
>variables to the SCGI server.  Perhaps we can make Quixote's
>scgi_server.py look for a PREFIX environment variable.  Then
>you could do something like this:
>
>    
>        SCGIServer 127.0.0.1 4000
>        SCGIHandler On
>        SetEnv PREFIX "/qx"
>    
>
>That would at least move the configuration information to a better
>place.
>
>

I was just thinking that this morning.  SetEnv would be perfect to give
this bit of extra configuration to the program.  Pity we have to set the
path twice, but at least they're easy to compare visually.  I didn't
know you can set a handler with mod_rewrite, but you can also set an
envvar with it, so it would solve that problem too.