apache nog handling 404 requests

[maever]

Hello everyone,

I'll jump straight to the question.
Our company is experimenting with their first cpanel servers.
We are currently experiencing an issue where apache no longer handles any 404 error request (or at least does not seem to be).

The browser displays an error message that the page could not be found (instead of apache reporting this).
With this said it also seems impossible to have custom 404 error pages.
(since the "page not found" message displays in the browser

We run latest Centos stable with an up2date installation of cpanel.
additionaly we have enabled suphp and installed mod_security and ConfigServer firewall.

My question is: what steps can we take in order to get custom 404 error pages working again and could any of our installed modules be the cause of these errors ?

My gratitude in advance to all who take the time to send in a reply.

[cPanelDavidG]

Hello everyone,

I'll jump straight to the question.
Our company is experimenting with their first cpanel servers.
We are currently experiencing an issue where apache no longer handles any 404 error request (or at least does not seem to be).

The browser displays an error message that the page could not be found (instead of apache reporting this).
With this said it also seems impossible to have custom 404 error pages.
(since the "page not found" message displays in the browser

We run latest Centos stable with an up2date installation of cpanel.
additionaly we have enabled suphp and installed mod_security and ConfigServer firewall.

My question is: what steps can we take in order to get custom 404 error pages working again and could any of our installed modules be the cause of these errors ?

My gratitude in advance to all who take the time to send in a reply.

The easiest way to implement a custom 404 page in cPanel is to go to the Advanced section and click "Error Pages" then clicking 404 where you can create a custom HTML page that can include server-side includes.

[maever]

Thank you for your reply.

I tried this but the problem seemed to be that Internet Explorer does not display 404 errors that are under 512 bytes.

So a 404 error pages has to exceed 512 bytes otherwise IE will display it's default "friendly" page-not-found message.