PATH_INFO is a CGI 1.1 standard, and it is often used as a carrier for passing parameters.
In Apache, with no configuration at all, AcceptPathInfo is accepted by default for PHP scripts, which means:
if the server has a /laruence/info.php
then for the following requests, Apache accepts them all:
/laruence/info.php/dummy /laruence/info.php/pathinfo
Under Nginx, by default Nginx does not support PATH INFO, meaning those requests will 404 with a file-not-found error.
with 0 CommentHow the Zend Engine turns HTML outside PHP tags into T_INLINE_HTML tokens and ZEND_ECHO opcodes (split into 400-character chunks), and how the '@' error suppression operator is compiled into two oplines that swap error_reporting(0) in and out around the statement.
with 0 CommentWhy must Xdebug be loaded as a Zend extension, and how does a Zend extension differ from a regular PHP extension? This article traces the full extension loading path in PHP 5, from php_module_startup and php_init_config down to php_dl, showing where php extensions and zend extensions are registered and started.
with 0 CommentPHP is often a poor fit for a resident SHELL process. It has no dedicated GC routine, and no effective path to memory management. So if you use PHP as a resident SHELL, you'll often be unhappy when memory exhaustion aborts the process.
And if the incoming data is invalid while the SHELL doesn't check it, causing an abort, that will make you unhappy too.
So? What do we do?
Multiple processes....