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!
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!