PHP-naming vs. HTML-naming

[RobertX]

Is it always necessary to name all your web pages PHPs, especially when some are not with PHP functionality?

[Sid]

No

[RobertX]

Thanks, that helps a lot (no, I'm not being sarcastic; I actually employ the habit of saving all my pages into the PHP format)!

[Moe]

There is no such thing as a "PHP format." They are all text files. Name them whatever you want.

[RobertX]

OK buddy, I will.

[Q91]

as long as the mime settings are correct, or the browser will probably try to download them

[Moe]

Mime settings are for what the server places in the content-type header for files it serves directly. It has no effect on what the server actually does with the file.

Other configuration directives determine how the server handles files that require additional server side processing.

The possibilities are infinite, which is why it doesn't matter.

[Sid]

It is less confusing to any humans other than yourself (and even to your own future self months or years down the line) to give files sensible titles, including appropriate file extensions.

[Moe]

GTFO with your sensibleness.

[Q91]

oh i've had MIME settings play tricks on me. Both server-side and client-side. If you rename it to a format that's not a standard PHP and the browser doesnt have any mime settings for it, the browser will either try to download it, or the server will try to block you from accessing the file. IIS does this, and apache will try to tell you to download it (atleast it did 6 years ago)