Legacy Path

Do not use this module; it is no longer supported. Consider using Path Redirect instead.

Legacy Path is intended to support websites that are moving to Drupal but have content that either won't be managed by Drupal immediately or at all, but must remain reachable through it's original URL. The assumption is made that the legacy system remains operational, but at a different (sub)domain or directory.

Note per #236414: Module does not work with 'Normal' caching enabled. that this module does not work with Normal caching enabled.

For example, an online newspaper might have an existing archive system that provides permalinks such as:
http://paper.example.com/content.php?section=12&article=22
After a Drupal installation, the online newspaper has moved the old system to the URL:
http://archive.example.com/content.php?section=12&article=22

This module accomodates redirecting (using HTTP redirects) the old URL to the new URL.

The module follows this flow:

1. An incoming URL is checked to see if it is present in Drupal. If the module is not set to force all paths to redirect, the module returns control to the normal Drupal request handling process.
2. The module then iterates through the redirect rules from lightest to heaviest checking for a matching pattern.
3. When a match is found, the module checks to see if the redirect URL is in the cache. If it is, and the cache entry is not expired, a redirect is sent to the browser and the module terminates. Otherwise, the module validates the new URL. If it is valid, the URL is cached, the redirect sent to the browser, and the module terminates.
4. If the match did not produce a valid URL, processing continues to the next redirect rule.
5. If no matches and/or no valid redirects are found, the module returns control of request handing to Drupal which can then produce the 404 response.

Credits

Development of this module is sponsored by Four Kitchens.