Unfortunately, I can't verify your question regarding suexec.c and building Apache as I have moved on from that organization and, frankly, can't remember. I've cc'd the current owners of the code. They may be able to help you.
On Friday, June 6, 2014 1:58:19 PM UTC-7, Charlie Brady wrote: > > > On Fri, 6 Jun 2014, Joel Martinez wrote: > > > I'm not sure of the apache version. I don't remember totally, but I > > wouldn't be surprised if it was a manual tweak to our suexec to increase > > security within our organization. > > You said "I enabled these and everything is working splendidly". Can you > verify that you edited suexec.c and rebuilt apache? Do you have before and > after versions of the code? > > > I would still recommend mentioning the requirement of these environment > > variables to exist somewhere in the Mojolicious docs. > > I don't think repeating the specification of the CGI belongs in the > Mojolicious docs. > > > On Friday, June 6, 2014 1:45:05 PM UTC-7, Charlie Brady wrote: > > > > > > > > > On Tue, 5 Feb 2013, Joel Martinez wrote: > > > > > > >> But it appears Mojolicious needs PATH_INFO, HTTPS or > SERVER_PROTOCOL, > > > >> and SCRIPT_NAME in it's routine. Do you have any clue why these > might > > > >> not be set as environment variables correctly? > > > > > > > > SOLVED! > > > > > > > > It turns out an apache module "suexec" was blocking these (and many > > > other) > > > > environment variables from being set. Turns out "suexec" has a > > > whitelist > > > > of environment variables that it allows. I enabled these and > everything > > > is > > > > working splendidly. > > > > > > What version of apache were you using? I see PATH_INFO, HTTPS, > > > SERVER_PROTOCOL and SCRIPT_NAME in safe_env_lst[] in suexec.c in > apache > > > 2.2.15 source code, so they are already whitelisted in that version. > > > > > > > On a side note... to save others the frustration I went through, > perhaps > > > > you could add some sort of sanity check for these environment > variables > > > in > > > > CGI mode. Seeing as how this parse_env function depends on them, it > > > would > > > > be nice to see some sort of error if they couldn't be found instead > of > > > > silently failing. > > > > > > If anyone knows of problems with request parsing/routing in CGI, > please > > > report via github issues. > > > > > > > > > > > Thanks for your help. > > > > > > > > On Tuesday, February 5, 2013 10:02:26 AM UTC-8, sri wrote: > > > > > > > > > > > If you want to work on this, all our test cases can be found > here. > > > > > > > > > > > > > https://github.com/kraih/mojo/blob/master/t/mojo/request_cgi.t > > > > > > > > > > And the actual parser is here. > > > > > > > > > > > > > > > > > > > https://github.com/kraih/mojo/blob/master/lib/Mojo/Message/Request.pm#L203 > > > > > > > > > > -- > > > > > Sebastian Riedel > > > > > http://twitter.com/kraih > > > > > http://mojolicio.us > > > > > > > > > > > > > > > > > > > > > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
