为什么.htaccess中来自toro php路由器的配置不起作用？

Question

the Toro docs show:

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond $1 !^(index\.php)
RewriteRule ^(.*)$ /index.php/$1 [L]

but i tryed many times and different ways, but, doesn't work... After a lot of searching i found this (source):

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond $1 !^(index\.php)
RewriteRule ^(.*)$ /index.php?$1 [L]

Just need to change in RewriteRule ^(.*)$ /index.php/$1 [L] the / to ? , to get this RewriteRule ^(.*)$ /index.php?$1 [L]

Someone know why the original doesn't work, or have a different aproach for this?

MORE INFO Host: php5.4 fastcgi, shared host, company Dreamhost. Just accept SCRIPT_NAME instead of PATH_INFO

the Toro code that handle it is:

$path_info = '/';
        if (!empty($_SERVER['PATH_INFO'])) {
            $path_info = $_SERVER['PATH_INFO'];
        }
        else if (!empty($_SERVER['ORIG_PATH_INFO']) && $_SERVER['ORIG_PATH_INFO'] !== '/index.php') {
            $path_info = $_SERVER['ORIG_PATH_INFO'];
        }
        else {
            if (!empty($_SERVER['REQUEST_URI'])) {
         $path_info = (strpos($_SERVER['REQUEST_URI'], '?') > 0) ? strstr($_SERVER['REQUEST_URI'], '?', true) : $_SERVER['REQUEST_URI'];
                }
        }

Answer 1

You probably are running on a server that doesn't support the PATH_INFO style of cgi. This is where the script itself is /index.php and the "PATH_INFO" is the pathname that comes after it. Take a look at the AcceptPathInfo documentation:

This directive controls whether requests that contain trailing pathname information that follows an actual filename (or non-existent file in an existing directory) will be accepted or rejected. The trailing pathname information can be made available to scripts in the PATH_INFO environment variable.

For example, assume the location /test/ points to a directory that contains only the single file here.html. Then requests for /test/here.html/more and /test/nothere.html/more both collect /more as PATH_INFO.

The primary purpose of the AcceptPathInfo directive is to allow you to override the handler's choice of accepting or rejecting PATH_INFO. This override is required, for example, when you use a filter, such as INCLUDES, to generate content based on PATH_INFO. The core handler would usually reject the request, so you can use the following configuration to enable such a script:

<Files "mypaths.shtml">
Options +Includes
SetOutputFilter INCLUDES
AcceptPathInfo On
</Files> 

So you could try turning AcceptPathInfo to "On" and see if that helps.