Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Add custom error pages and fastcgi intercept errors #85

Open
iio7 opened this issue Oct 20, 2021 · 0 comments
Open

Feature request: Add custom error pages and fastcgi intercept errors #85

iio7 opened this issue Oct 20, 2021 · 0 comments

Comments

@iio7
Copy link

iio7 commented Oct 20, 2021

httpd is almost useless for anything other than static HTML files. Even though you can use it with fastcgi, there is no way to intercept errors and display a custom error page to a user whenever a 500 error occurs.

Custom error pages (not only 404) is needed.

Also a way for fastcgi to intercept the error so that it can be handled gracefully on production servers.

NGINX does this with fastcgi_intercept_errors on;

Last but not least, the error logging without using syslog doesn't provide any timetamps or IP addresses, or at least a way to disable enabled these. Using syslog clutters the log file.

Anyway, these things are very much needed for a production system running more than just static files.

Someone has already made some patches for httpd please see https://github.com/mpfr/httpd-plus

Other than that, httpd is a great product, the setup and logical configuration is amazing! Well done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant