FoxIDs Request for non-existing routes results in unhandled exception logged

This happens routinely due to sporadic crawler/scanner requests. For example I see requests for paths like /sito/wp-includes/wlwmanifest.xml.

Shouldn't this be more gracefully logged as a trace with level warning or something?

IMHO, it would be good to keep unhandled exceptions to unexpected things that might warrant investigation.

Apr 23 '25 17:04 bjornharrtell

Calls like this should be logged as warnings with the Log RouteException as warnings commit https://github.com/ITfoxtec/FoxIDs/commit/76cba5decded52b27436902e1c16ac398f750833 from version 1.15.22.

Apr 25 '25 13:04 Revsgaard

@Revsgaard I don't think that helps for this and similar cases, as it doesn't appear to be a RouteException that is thrown. See fx:

Apr 25 '25 14:04 bjornharrtell

If https://foxids.com/sito/wp-includes/wlwmanifest.xml is called on FoxIDs Cloud it result in this log in the master tenant:

Jul 13 '25 08:07 Revsgaard

@Revsgaard seems like most of them are gone since some time ago yes.

However, I still spot some edge cases, for example:

and:

Jul 13 '25 18:07 bjornharrtell