index.html and index.php not co-habitating

  • This seems more of a server environment issue to me, but I’m hopeful someone has ran into this WordPress scenario.

    I’ve installed WordPress 2.91 in the root directory of a site (BSD-Linux, Apache) resulting in the site’s existing index.html and WP’s index.php being in the same directory.

    When the URL is viewed with no file name, the static index.html is served, how it should be. but when index.php is requested, the web server redirects to no file name, resulting in the index.html being served.

    I’ve looked for a mod rewrite rule that might explain this and there aren’t any in my .htaccess file.

    Anyone know of way to fix this? mod-rewrite rules to compensate maybe?

Viewing 2 replies - 1 through 2 (of 2 total)

  • @dewed, it is a server thing, many prioritize index.html over index.php files. In your case, either delete index.html or rename it.

    Thread Starter Dewed

    (@dewed)

    hrm. I can control which to serve by default in the .htaccess with the DirectoryIndex directive The point is, I should not have to make an either or choice, serve index.html if no file is requested, otherwise serve the requested file, in this case index.php

    Thanks anyways

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘index.html and index.php not co-habitating’ is closed to new replies.

Tags