09-18-2023, 10:23 PM
I may have expressed myself a bit unclearly.
My NOT FOUND HANDLER is always triggered when a file is requested from an IP address that does not exist on the server.
The HANDLER stores the IP address, the time of the first error and the number of errors. In addition, the session created is terminated immediately.
If too many such files are requested for an IP address within a certain time interval, this IP address will be temporarily blocked.
This has certainly worked so far, even for PHP files!
However, recently the NOT FOUND HANDLER no longer triggers for PHP files,
but only the INTRAWEB standard handler for 404, which does not terminate the created sessions immediately and does not recognize brute force attacks.
It seems like my HANDLER is no longer called for files whose file extension is blocked by INTRAWEB!
If I unblock PHP or other extensions, my HANDLER will trigger again.
My NOT FOUND HANDLER is always triggered when a file is requested from an IP address that does not exist on the server.
The HANDLER stores the IP address, the time of the first error and the number of errors. In addition, the session created is terminated immediately.
If too many such files are requested for an IP address within a certain time interval, this IP address will be temporarily blocked.
This has certainly worked so far, even for PHP files!
However, recently the NOT FOUND HANDLER no longer triggers for PHP files,
but only the INTRAWEB standard handler for 404, which does not terminate the created sessions immediately and does not recognize brute force attacks.
It seems like my HANDLER is no longer called for files whose file extension is blocked by INTRAWEB!
If I unblock PHP or other extensions, my HANDLER will trigger again.