*.php/anyresponce

[dims]

We have the strange problem, for example if put anything after .php script - open content of this script
http://domain.tld/index.php/adasdasdasasdasd/asdasdasd/asdasd
Litespeed enterprise 4.2.1
Centos 6 x86_64

 

[dims]

like as AcceptPathInfo on

 

[NiteWave]

did simple tests:

it's default behavior of Apache as well

e.g, the default is
AcceptPathInfo Default
http://httpd.apache.org/docs/current/mod/core.html

Default
       The treatment of requests with trailing pathname information is determined by the handler responsible for the request. The core handler for normal files defaults to rejecting PATH_INFO requests. Handlers that serve scripts, such as cgi-script and isapi-handler, generally accept PATH_INFO by default.

my test show that
AcceptPathInfo On/Off
no effect to lsws. lsws just stick to "AcceptPathInfo Default"

and test show that if the php script has query string,
AcceptPathInfo On/Off
also no effect to apache.

for example,
domain.com/hello.php?a=1/aaa/sss/ddd/fff
the behavior are same between apache and lsws

 

[dims]

did simple tests:

it's default behavior of Apache as well

e.g, the default is
AcceptPathInfo Default
http://httpd.apache.org/docs/current/mod/core.html

Default
       The treatment of requests with trailing pathname information is determined by the handler responsible for the request. The core handler for normal files defaults to rejecting PATH_INFO requests. Handlers that serve scripts, such as cgi-script and isapi-handler, generally accept PATH_INFO by default.

my test show that
AcceptPathInfo On/Off
no effect to lsws. lsws just stick to "AcceptPathInfo Default"

and test show that if the php script has query string,
AcceptPathInfo On/Off
also no effect to apache.

for example,
domain.com/hello.php?a=1/aaa/sss/ddd/fff
the behavior are same between apache and lsws

This is will be fixed?

 

[mistwang]

It is not likely be changed, however, you can easily address it with a rewrite rule, by testing the PATH_INFO env with RewiteCond directive.