Every once in a while ERROR --> ApplicationException: Invalid controller path end up in the log files like mentionned in an earlier issue , because of non-existing files (when they cannot be served they go through the index to resolve as controller paths).
With the current minimalistic logging it can be tedious to find out where they came from. Would it be an option to add to the log message the invalid controller path itself - and/or to make that logging behavior mutable. Like in the earlier report it can be good to know which file is missing/trailed/... to solve that issue itself, but on the other hand missing files can happen (hardcoded images, installations duplicated on other environments without full copy of media,...) and would flood the logs (where the browser can report the missing file visually and/or in network logs). Broken media is not that critical.
Every once in a while ERROR --> ApplicationException: Invalid controller path end up in the log files like mentionned in an earlier issue , because of non-existing files (when they cannot be served they go through the index to resolve as controller paths).
With the current minimalistic logging it can be tedious to find out where they came from. Would it be an option to add to the log message the invalid controller path itself - and/or to make that logging behavior mutable. Like in the earlier report it can be good to know which file is missing/trailed/... to solve that issue itself, but on the other hand missing files can happen (hardcoded images, installations duplicated on other environments without full copy of media,...) and would flood the logs (where the browser can report the missing file visually and/or in network logs). Broken media is not that critical.