使用index.php而不是index.html是不好的做法吗？

Question

I'm not sure why it should be, but index.html feels 'right'. I'm using index.php because if my login fails, I want to return to index.php and show the returned error on in the initial log-in page, like this...

<?php
   if(isset($_GET["loginFailed"])) {
      echo ($_GET['reason']);
   }
?>

That's trimmed a bit, but the 'reason' will be deciphered by the php and a user-friendly error shown.

The login error is just returned from my 'login.php' with something like..

if($row === false) {
    die(header("location:index.php?loginFailed=true&reason=usernamenotfound"));
}

This all works fine, but I have to keep the index named as index.php instead of index.html. If I change it to index.html, the php part is just ignored.

Is there anything wrong with my approach? Is it unsafe or anything?

Answer 1

No issue with using index.php instead of index.html . It does not affect search engine rankings - So the only reason you would want to change it is for aesthetics.

If you want to use index.html instead of index.php , there are two options:

Firstly, you can rewrite extensions using .htaccess. Add the following lines to your .htaccess, and they will remap all requests for a .html page to a .php one without the URL changing.

RewriteEngine on
RewriteRule ^(.*)\.html$ $1.php [nc]

Secondly, you can allow .html files to be parsed by the PHP interpreter. To do this, add one of the following lines to your .htaccess (Different hosts have different syntax, the first works for most shared hosts)

AddHandler application/x-httpd-php5 .html .htm

AddType application/x-httpd-php .html .htm

AddHandler application/x-httpd-php .html .htm