Question

Prevent ERROR - Connector: 404 - file not found for file: ... in the logs

9

Lots of the apps I am working on have tons of messages in the logs like this ERROR - Connector: 404 - file not found for file: apisix/batch-requests These are mostly bad people trying to get information about any app, looking for weak spots. It is not too big a concern, since there are lots of easy ways to find out the type of platform that is running the app. But is there a way to change the response and not log it? Can everybody please upvote Johan Mattsson ‘s idea on this: https://community.mendix.com/p/ideas/15762598695817640

asked 2022-04-24

Tim v Steenbergen

4 answers

Ronald Catersels · Answer 1 · 2022-04-24

Imho Mendix should fix these. They should filter these URL's already on all incoming traffic. All the logs of all the Mendix applications are crawling with these exact same URL's so they should have a pretty good picture on which URL's they should block.

Regards,

Ronald

Matt Marich · Answer 2 · 2025-04-14

At the moment these 404 logging events are really only helpful for diagnosing actual missing files. From the security standpoint these messages are non-usable as they don't included client ip, http referrer, etc. It would be nice to have some options to tune this via Runtime Customization parameters or with an environment variable usable within the docker mendix buildpack.

In my opinion, an on/off toggle for 404's should exist but additional information should be provided in the 404 message. Also, you should be able to negate 404's should a particular header be passed (helpful for negating messages when your own scheduled vulnerability scans are ran).

Sebastiaan den Boer · Answer 3 · 2025-05-01

At the very least, a 404 shouldn't be classified the same as a 5xx error from an HTTP perspective, since a 404 like many other 4xx codes indicate that the request is not valid, unauthorized, incomplete, etc.

Right now, these 404 logs are noted as ERROR, which is generally reserved in the Mendix Docs for a problem that requires immediate attention. In my opinion, a WARNING classification is more fitting here, since it *might* indicate a problem, but does not impact whether the application is working correctly. https://docs.mendix.com/refguide/log-levels/#level

The log level change is trivial and should be fixed ASAP if this is generally agreed upon, but I would also expect a blacklisting option in the future.

Volker Schlecht · Answer 4 · 2022-05-06

Personally I *do* want to see in my logs when someone is scanning my application.

What I would appreciate as a feature is if Mendix provided an option to directly blacklist TCP connections from addresses listed on a few reliable IP blocklists. That should cut out most of the log noise caused by botnets.