I hope that's wrong. As for your example below, you would send "more_path/file.py/even_more_path/file.pl" to the "/path/file.php" script. It is not the server's concern how the path is handled. As for complexity, this doesn't make sense to me. Apache still has to parse the path to determine if it is valid. Once it encounters the "file.php", it should stop there. It knows that this is a file and not a directory. It knows what to do with these files. That should be all that apache needs to know.
<s> I hope that they at least add(ed) a compatibility flag for this if you are right... --- Seairth Jacobs [EMAIL PROTECTED] "Brian 'Bex' Huff" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Id advise against using this kind of architecture. > > Its my understanding that Apache2 will no longer allow this kind of CGI > trick in its new fangled high-speed filter model... its too hard to tell > which module is supposed to be executed first. For example: > > /path/file.php/more_path/file.py/even_more_path/file.pl > > what the heck should Apache do with this? > > If you do this, you'll be stuck using Apache 1.3 forever, which is > slower than IIS on Windows, and much slower than Apache 2. > > If Im wrong, somebody please correct me, but I think its because people > keep writing CGI apps like this that the migration to Apache 2 will be > so painful... > > -- > > Brian 'Bex' Huff > [EMAIL PROTECTED] > Phone: 952-903-2023 > Fax: 952-829-5424 > > > As I understand it, it would allow me to do the following: > > > > /path/file.php/more_path/ > > > > Where PATH_INFO would be equal to "more_path/", instead of > > "/path/file.php/". Right now, I get an error back from the above, giving > > the following message: > > > -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
