I know this has been brought up before but I have not found a solution for the issue. If a non-existent module route is called (for example in our site: /login/mailto:support) then it throws an error. It does set the invalidevent and the currentView to 404 but is still throwing the error.
We get bots that will hit all kinds of combinations which in turn creates tons of error emails. Is there something baked in to fix this?
Error:
Thank you for any help!
What version of Coldbox? I believe @lmajano lowered the log level for 404s to warn on the latest Coldbox release
Coldbox 7.2. And regardless of the logging it is throwing a site wide exception setting the moduleLayoutPath variable each time the url of an invalid module event is hit.
Oh, that’s a different error. Do you have an invalidEventHandler setting in your coldbox config?
I do: invalidEventHandler : “main.onMissingTemplate”,
Could you file a bug report for this. I can see what’s going on with the URL above, I think. The presence of the colon is causing coldbox to think it’s a module route pattern. We should treat that like any other 404
I can do that…can you just let me know which URL is the most current place to do a Coldbox bug report? Thanks.
