Strange URL separation

Hi,

a friend of mine is trying to move his website to my server. This site
contains some PHP scripts which are called in an uncommon way, eg:
http://xxxx/path1/path2/script.php/login

In this case, /login should be passed to script.php

This was running with Apache 1.3.27 / PHP 4.3.3 but seems not to work
on my combination of Apache 2.0.46 / PHP 4.3.2

Is there a parameter I can set to have the same behaviour? Or is this
simply impossible with Apache 2?

Thanks,

Ralf

r.koch@formel4.de (Ralf) writes:

> a friend of mine is trying to move his website to my server. This site
> contains some PHP scripts which are called in an uncommon way, eg:
> http://xxxx/path1/path2/script.php/login
>
> In this case, /login should be passed to script.php
>
> This was running with Apache 1.3.27 / PHP 4.3.3 but seems not to work
> on my combination of Apache 2.0.46 / PHP 4.3.2

What does "seems not to work" mean? What happens? How is the PHP
script attempting to retrieve /login? Does the script assume that
PHP's register_globals is on, but it's disabled (as it should be)
on the site where the script doesn't work?

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

"Michael Fuhr" <mfuhr@fuhr.org> schreef in bericht
news:41b9fef6$1_2@omega.dimensional.com...
> r.koch@formel4.de (Ralf) writes:
> > a friend of mine is trying to move his website to my server. This site
> > contains some PHP scripts which are called in an uncommon way, eg:
> > http://xxxx/path1/path2/script.php/login
> > In this case, /login should be passed to script.php
> > This was running with Apache 1.3.27 / PHP 4.3.3 but seems not to work
> > on my combination of Apache 2.0.46 / PHP 4.3.2
> What does "seems not to work" mean? What happens? How is the PHP
> script attempting to retrieve /login? Does the script assume that
> PHP's register_globals is on, but it's disabled (as it should be)
> on the site where the script doesn't work?
Or is apache2 configured to not-accept path info ..
http://httpd.apache.org/docs-2.1/mod...acceptpathinfo

http://httpd.apache.org/docs-2.0/upgrading.html
" The handling of PATH_INFO (trailing path information after the true
filename) has changed for some modules. Modules that were previously
implemented as a handler but are now implemented as a filter may no longer
accept requests with PATH_INFO. Filters such as INCLUDES or PHP are
implemented on top of the core handler, and therefore reject requests with
PATH_INFO. You can use the AcceptPathInfo directive to force the core
handler to accept requests with PATH_INFO and thereby restore the ability to
use PATH_INFO in server-side includes. "

HansH