On Thu, Oct 17, 2013 at 12:59 PM, Stephan Beal <[email protected]>wrote:
> On Thu, Oct 17, 2013 at 6:37 PM, Ben Summers <[email protected]> wrote: > >> and of course, Jetty isn't sending a REQUEST_URI. This environment >> variable isn't part of the CGI 1.1 spec, so I suppose we can excuse Jetty >> for not sending it: >> >> http://tools.ietf.org/html/rfc3875 >> >> It looks like the addition of SCGI support in >> http://www.fossil-scm.org/fossil/info/a2e7472d0fa04132 added the >> requirement for REQUEST_URI. >> >> Which one of fossil or Jetty needs fixing? >> > > i don't have a definitive answer (i'd never heard of SCGI before those > patches arrived) but do have a tiny bit more info which might help someone > else... > > http://en.wikipedia.org/wiki/Simple_Common_Gateway_Interface > > shows an example which implies that REQUEST_URI is indeed required by > SCGI. As Ben says, though, it's not part of CGI. > > My suspicion is that Fossil needs to be fixed but that this hasn't yet > been seen because Apache and friends provide REQUEST_URI even in CGI mode. > i'll see if i can get an SCGI environment running here to try this out > (apache appears to have a mod_scgi... let's see what that does...). > > i can't make any promises, but i'm looking into it. > > Apparently we construct REQUEST_URI by appending PATH_INFO to SCRIPT_NAME. The three are related. Currently, Fossil requires REQUEST_URI and SCRIPT_NAME at a minimum, and will construct PATH_INFO from those two if it is missing. I'm working on a patch to construct REQUEST_URI from SCRIPT_NAME and PATH_INFO if REQUEST_URI is missing instead. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
