Open alexander-schranz opened 8 years ago
Sounds like a great idea! But we have to think about how to handle all the discovery requests like /phpmyadmin
. We probably have to check if there is already a webspace configured for this URL, and it would probably also be a good idea to have a blacklist.
And when we finally release that we should not forget to put that into the kernel.terminate
event, so that the response time doesn't get worse :-)
and the content manager create a redirect to a specific page / url.
As pages with internal url target? Or with a redirect settings module?
Such an error log is indeed quite standard. The most useful ones I've seen let you either discard errors only once (in that case all errors of the same type are removed) or discard them forever (all errors of the same type are removed, future errors are not shown in the log).
Tracking and grouping 404 requests and make it easy to create a Redirect for this url would maybe something which could be implemented in the SuluRedirectBundle and an optional activateable feature /cc @wachterjohannes
@alexander-schranz Sounds reasonable, should we move that issue then?
Yeah will move the issue to the redirectbundle
Mostly when you create a new website you can not create for all old urls redirects. It would be good to have a 404 url list in the backend foreach webspace with a counter (which urls was called most) and the content manager create a redirect to a specific page / url.