- Issue created by @emilymathew
- 🇩🇪Germany Anybody Porta Westfalica
@emilymathew did you have a look at 🐛 Return a "real" Symfony 404 response object instead of mimicking it Fixed already regarding this?
The search404 module is supposed to return 404 HTTP response even if it shows the search results. Currently it works with core search module. If custom search path is given, the search results page return HTTP response status 302 instead of 404.
Enable "Do a "Search" with custom path instead of a Drupal Search when a 404 occurs" and input a custom search path. Then save the configuration and access a non existing URL. The expected HTTP response is 404, but here it returns 302.
We may need to handle it as a HTTP sub request as it is implemented in Drupal core for the "Default 404 (not found) page" settings in "Basic site settings".
Active
2.0
Code
@emilymathew did you have a look at 🐛 Return a "real" Symfony 404 response object instead of mimicking it Fixed already regarding this?