Hello Everyone,
We analyze the cause of the issue, and evaluate solutions to prevent the same problem from happening again in the future whenever something like this happens. For this particular issue, we've already started work on incorporating an additional automated script during the QA process that checks for the specific scenario associated with case EA-7980.
You are correct, and I'd like to thank you for taking the time to explain the details of the issue. The change stemmed from a case that was opened to address an issue where ErrorDocument directives were not honored for .php files when using PHP-FPM.
For anyone interested, the new case to address that issue (since the previous one was reverted) is CPANEL-23574.
Thank you.
We analyze the cause of the issue, and evaluate solutions to prevent the same problem from happening again in the future whenever something like this happens. For this particular issue, we've already started work on incorporating an additional automated script during the QA process that checks for the specific scenario associated with case EA-7980.
Hi @Dean999,The intent of this rule is to mark non-existent (file-not-found) PHP scripts as text/html, so that they generate precisely the same "Not Found" message as other missing files. (This appears to be the only purpose of the rule, AFAIK).
You are correct, and I'd like to thank you for taking the time to explain the details of the issue. The change stemmed from a case that was opened to address an issue where ErrorDocument directives were not honored for .php files when using PHP-FPM.
For anyone interested, the new case to address that issue (since the previous one was reverted) is CPANEL-23574.
Thank you.