This project is not covered by Drupal’s security advisory policy.


When porting a static HTML site to a Drupal site, you often encounter this problem:

For the legacy site, it has a link: and you do not want to change this link; and its Apache configure file declares that DirectoryIndex index.html, index.php.

On the new new Drupal site, you create a node with nid = 100 and duplicate the content of Thanks to Path module and Clean URL feature, you can set's URL path as path/to/directory/index.html.

By doing this, you guarantee that a visit to gets the same content as

So far, so good.

But what if your visitors go to Unfortunately, as they are visiting a path alias, not a physical path, they will not be able to get automatically, even on the new Drupal site's Apache configure file, it also declares that DirectoryIndex index.html, index.php, as it only works for physical directory.

Worse more, in many cases, instead of is provided to visitors.

Therefore, after porting the site, we must make sure that a visit to must be able to locate DirectoryIndex files declared by the legacy site.

For example, if a legacy site declares that DirectoryIndex index.html, index.php, then for visits to, Drupal must first look for, and if not found, try again. If still not found, gives 404 Page Not Found error.

Sometimes, for somehow, we want to redirect all 404 visits to another website. For example, if is not found, we want to redirect visits to to see if this URL exists.

About this module

This module is developed to fix aforementioned problem. You can tell the module what string (file name) is to be appended to the end of a path if given path is not found.

For example, given path is and legacy site declares that DirectoryIndex welcome.htm, index.html. If does not exist, the module will try to find URL path and respectively. If both fails, and if an external site is specified, this module will redirect visits to to see if it exists.

See also

Project Information

  • Maintenance status: Unknown
  • Development status: Unknown
  • Downloads: 892
  • Last modified: 27 November 2014
  • shield alertThis project is not covered by the security advisory policy.
    Use at your own risk! It may have publicly disclosed vulnerabilities.