I'm just curious, how's feature of apache is known as that's pointing demands such as this

www.example.com/index.php/my/path/here

to some file index.php? In the first moment, you may think, that it might be correct if the request results in 404 error page because there's no folder known as index.php to begin root dir.

BTW, it is possible to possible ways to switch off this Apache feature (if it's an element) to ensure that such demands really finish track of 404?

This is not a URL rewrite feature. Or at best it does not need to become. See AcceptPathInfo Directive:

This directive controls whether demands which contain trailing pathname information that follows an actual filename (or non-existent file within an existing directory) is going to be recognized or declined. The trailing pathname information can be created open to scripts within the PATH_INFO atmosphere variable.

For instance, assume the place /test/ points to some directory that consists of just the single file here.html. Then demands for /test/here.html/more and /test/nothere.html/more both collect /more as PATH_INFO.

It had been initially a CGI atmosphere variable.

  • PATH_INFO

The additional path information, as given through the client. Quite simply, scripts could be utilized by their virtual pathname, then extra information in the finish of the path. The additional details are sent as PATH_INFO. These details should be decoded through the server whether it comes from the URL prior to it being passed towards the CGI script.

Make reference to this link to have an explanation.

It's a approach to passing information towards the (within this situation) index.php script without utilizing a query string, which may be overlooked by some search engines like google, hence the title of this article "Internet Search Engine-Friendly Web addresses".

I'm able to recommend the 3rd method talked about within the article since it eliminates strange searching Web addresses with index.php in the centre.

It's there that you'll have a file like index.php look into the PATH_INFO in the server and handle an entire tree of content. While there is no way I understand of to power it down, you can just have index.php look into the non-empty $_SERVER['PATH_INFO'] and respond having a 404 code through the header() function.