By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,347 Members | 1,390 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,347 IT Pros & Developers. It's quick & easy.

apache 1.3.x and the php file extension

P: n/a
A curious observation:

I have my apache web server configured for the PHP apache module to
parse files ending in the .php extension.

nothing unusual about that, but I also noticed that if I leave the file
extension off completely, not only does apache map it to the
corresponding php file, but it allows the php module to parse it
accordingly.

for instance...
Lets say I have a file called foo.php in the document root. Normally, I
could access it like so
http://localhost/foo.php
but as it turns out, I can also access it like so
http://localhost/foo
and I do not have any folders off the document root named "foo".

I'm using apach 1.3.24 with PHP v4.3.2-RC1 running on windows XP pro SP1

Jul 16 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Terence,

that's Apaches multiview feature.
See http://httpd.apache.org/docs/content-negotiation.html

Cheers
Frank

Terence wrote:
A curious observation:

I have my apache web server configured for the PHP apache module to
parse files ending in the .php extension.

nothing unusual about that, but I also noticed that if I leave the file
extension off completely, not only does apache map it to the
corresponding php file, but it allows the php module to parse it
accordingly.

for instance...
Lets say I have a file called foo.php in the document root. Normally, I
could access it like so
http://localhost/foo.php
but as it turns out, I can also access it like so
http://localhost/foo
and I do not have any folders off the document root named "foo".

I'm using apach 1.3.24 with PHP v4.3.2-RC1 running on windows XP pro SP1


Jul 16 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.