Req #27346 [Fbk->NoF]: can't capture error code - should be 403?

Edit report at https://bugs.php.net/bug.php?id=27346&edit=1 ID: 27346 Updated by: php-bugs@lists.php.net Reported by: douglas at gpc dot edu Summary: can't capture error code - should be 403? -Status: Feedback +Status: No Feedback Type: Feature/Change Request Package: *General Issues Operating System: Tru64 5.1 PHP Version: 4.3.4 Private report: N New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Re-Opened". Thank you. Previous Comments: ------------------------------------------------------------------------ [2017-01-20 20:19:51] heiglandreas@php.net Is this still relevant? ------------------------------------------------------------------------ [2004-02-22 08:03:20] douglas at gpc dot edu Description: ------------ We have all or .htm and .html (as well as .php, ...) files go through php. When a person creates a web page and saves the file with the wrong permissions so that they are not accessable by the httpd daemon, instead of giving an error like 403, the page returned is: Warning: Filed opening '/users/johndoe/public_html/x.html' for includsion (include_path=".:/usr/local/etc/php') in Unknown on line 0 The file (unix) is mode 600. If we change it to 644, there is no problem. Should not this be returned so that an error handler can handle it, such as 403 code? Please note the above error came from: http://www.gpc.edu/~johndoe/x.html (this is not a real link, but that is the format of the link.) Reproduce code: --------------- Not (php) code related - file system permission. Expected result: ---------------- The expected result is that this would be caught by 403 error code. Actual result: -------------- It gives a php result that it can't include the file. Is there a separate php error code list we should capture in config files? Basically, we want a cleaner way of handleling such errors so that it makes more sense to the visitor to a page, such as the 403 error for normal apache would do. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=27346&edit=1