Module Description
This module allows you to specify domains that should be attempted as a fallback to find content when a "404 page not found" error is encountered on your site.
This module is useful when you are doing a gradual migration to Drupal from another site (Drupal-based or not).
Let's say you have a legacy system which contains most of your web presence and decide to migrate to Drupal, starting with the home page, but didn't want to orphan the legacy site.
So, a URL such as https://www.example.com/department would stop working and would return 404 to users visiting the site.
If you specify legacy1.example.com and legacy2.example.com as your possible destinations for your Drupal site on example.com and a user visited example.com/department, a path which does not exist, Not Found Passthrough would then try legacy1.example.com/department if found, the user would be redirected. If not found, legacy2.example.com/department would be tried, and if found, the user would be redirected to that URL instead. If still not found, a custom 404 error page may be specified or a user message defined. You could also specify a site search URL as an option, so if a visitor tries to go to www.example.com/department and no servers are found that know what to do with the request, the user is taken to the search results page for department (example: www.example.com/search/department)
Usage
1. Install and enable the module. 2. Configure the module settings such as legacy servers, fallback 404 page, etc through 'Configuration -> Search and Metadata -> Page Not Found Passthrough (Redirect on 404)' 3. Configure the site to use the module by setting the 'Default 404 (not found)' page to /notfoundpassthrough in 'Configuration -> System -> Basic site settings'
The final step may be made obsolete in a future version of the module.
Incompatibilities
Requests which are handled with the Fast 404 module are not be handled by Redirects 404. Fast 404 "runs first" and the handles the requests on its own.
Alternatives
With mod_rewrite in Apache, it is possible to redirect 404s to an external URL, but it does not preserve the full request path nor support multiple destination servers.
History
Page Not Found Passthrough is the Drupal 8, 9, 10, ∞ port of Redirect 404.
This module is useful when you are doing a gradual migration to Drupal from another site (Drupal-based or not).
Let's say you have a legacy system which contains most of your web presence and decide to migrate to Drupal, starting with the home page, but didn't want to orphan the legacy site.
So, a URL such as https://www.example.com/department would stop working and would return 404 to users visiting the site.
If you specify legacy1.example.com and legacy2.example.com as your possible destinations for your Drupal site on example.com and a user visited example.com/department, a path which does not exist, Not Found Passthrough would then try legacy1.example.com/department if found, the user would be redirected. If not found, legacy2.example.com/department would be tried, and if found, the user would be redirected to that URL instead. If still not found, a custom 404 error page may be specified or a user message defined. You could also specify a site search URL as an option, so if a visitor tries to go to www.example.com/department and no servers are found that know what to do with the request, the user is taken to the search results page for department (example: www.example.com/search/department)
Usage
1. Install and enable the module. 2. Configure the module settings such as legacy servers, fallback 404 page, etc through 'Configuration -> Search and Metadata -> Page Not Found Passthrough (Redirect on 404)' 3. Configure the site to use the module by setting the 'Default 404 (not found)' page to /notfoundpassthrough in 'Configuration -> System -> Basic site settings'
The final step may be made obsolete in a future version of the module.
Incompatibilities
Requests which are handled with the Fast 404 module are not be handled by Redirects 404. Fast 404 "runs first" and the handles the requests on its own.
Alternatives
With mod_rewrite in Apache, it is possible to redirect 404s to an external URL, but it does not preserve the full request path nor support multiple destination servers.
History
Page Not Found Passthrough is the Drupal 8, 9, 10, ∞ port of Redirect 404.
Module Link
Project Usage
52
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
This module attempts to solve the issue of '404 page not found' errors by allowing users to specify fallback domains to find content when encountering such errors on their site during a migration process.
Data Name
notfoundpassthrough
OPENAI CHATBOT
OPENAI CHATBOT
