array ( 0 => 'index.php', 1 => 'PHP Manual', ), 'head' => array ( 0 => 'UTF-8', 1 => 'tr', ), 'this' => array ( 0 => 'security.cgi-bin.shell.php', 1 => 'Case 4: PHP parser outside of web tree', 2 => 'Case 4: PHP parser outside of web tree', ), 'up' => array ( 0 => 'security.cgi-bin.php', 1 => 'Installed as CGI binary', ), 'prev' => array ( 0 => 'security.cgi-bin.doc-root.php', 1 => 'Case 3: setting doc_root or user_dir', ), 'next' => array ( 0 => 'security.apache.php', 1 => 'Apache\'ye modül olarak kurulum', ), 'alternatives' => array ( ), 'source' => array ( 'lang' => 'en', 'path' => 'security/cgi-bin.xml', ), 'history' => array ( ), ); $setup["toc"] = $TOC; $setup["toc_deprecated"] = $TOC_DEPRECATED; $setup["parents"] = $PARENTS; manual_setup($setup); contributors($setup); ?>

Case 4: PHP parser outside of web tree

A very secure option is to put the PHP parser binary somewhere outside of the web tree of files. In /usr/local/bin, for example. The only real downside to this option is that you will now have to put a line similar to: 

#!/usr/local/bin/php
as the first line of any file containing PHP tags. You will also need to make the file executable. That is, treat it exactly as you would treat any other CGI script written in Perl or sh or any other common scripting language which uses the #! shell-escape mechanism for launching itself.

To get PHP to handle PATH_INFO and PATH_TRANSLATED information correctly with this setup, the cgi.discard_path ini directive has to be enabled.