Re: [Chicken-users] scgi with lighttpd

[Thomas Chust]

On Sun, 24 Sep 2006, Ashish Shrestha wrote:

> I am using scgi with lighttpd 1.4.11 and really enjoying it. [...] Don't 
> know the reasons for it but I think, specially for those using lighttpd, 
> it would be more helpful to use script_name or request_uri rather than 
> path_info as path_info is always empty. [...]

Hello Ashish,

I investigated this problem further and came to the conclusion that it is 
probably unnecessary to modify the SCGI egg, because lighttpd can easily 
be configured to behave as expected by the egg.

If you attach your SCGI with a command like

        scgi.server = ( "/some/root/path/" =>
                        (( "host" => "localhost"
                           "port" => 1234 )))

in the lighttpd configuration, then only SCRIPT_NAME is set by lighttpd, 
but if you omit the trailing slash in the configuration command like this:

        scgi.server = ( "/some/root/path" =>
                        (( "host" => "localhost"
                           "port" => 1234 )))

then a request for /some/root/path/some/path will set PATH_INFO to 
/some/path just as the SCGI egg expects it.

At least this works with a freshly installed lighttpd 1.4.12 on my Mac and 
it is documented behaviour.

Please let me know if this helps with your problem or whether you still 
need some fix incorporated into the SCGI egg.

cu,
Thomas