[eluser]jrlooney[/eluser]
Hi Fuzzy, thank you for replying. i've been banging my head over this for a couple days so I appreciate any input and attempt to troubleshoot it.
So the interesting thing is that CI calls the perl script and the perl script calls a generic PHP script (not CI), but CI is still doing its thing on that generic PHP call. And that is why i'm weirded out.
So when I output the value of `$phppath $scriptpath $scenario`; I get this (which is correct if I were gonna run that command on command line - "demo" is the scenario for the site I am compiling)
/usr/bin/php /home/acuweb/public_html/cgi-bin/aw/generatesuperfish.php demo
And quite literally that perl script is making a system call to php - but CI is somehow still monitoring things and chokes on that call. Because in the perl script, the system call looks like this:
Code:
my $output = `$phppath $scriptpath $scenario`;
and if i dump out the value of $output immediately after that line, it has the value "Content-type: text/html The URI you submitted has disallowed characters"
Sorry one detail I left out - this set up has been running on my server w/o issue for a couple years now. I am in the process of moving all my code to a new host and that is where this issue is happening. I am using the very same version of CI as I had previously, however this new host has the latest version of PHP running - which might be my issue. HOwever, I still think it's weird that CI is still checking URLs when CI calls a perl script which calls a generic php script.
Also of note, in that CI view file (that sends the system command for the perl script), I also tried setting CI's permitted URI chars at runtime so that it'd ignore them. But then what happens is I get CI's generic 404 error.
Code:
$this->config->set_item('permitted_uri_chars', '');
