On 12/14/05, Vincent Jong <vjong@xxxxxxxxxxxxxxxxx> wrote: > I've upgraded to Apache 2.2.0 for *nix and I've come across a wierd behavior > dealing with the 500 error page - it's being displayed on the browser as html > code. I have not done any configuration in regards to error documents and > this was not happening on version 2.0.55 which also did not have any error > document configuration. All other error pages are rendering normally (such as > 400 errors, etc...). To make sure it wasn't some configuration I missed, I > used the httpd.conf in the original directory and restarted apache and the > problem still existed with the original httpd.conf file. I guess, my > questions are, is this a known issue and is there a workaround for getting > the 500 error document to render correctly? I was on the #apache IRC room and > there wasn't much help for me there as I tried to get someone else to > reconfirm this. The easiest way to see this, which I was doing, was to change > the permissions of a script in cgi-bin to 644 and then try to access the > script. I can't replicate this problem. Try using the default config file that comes with 2.2.0 and see if you can recreate it. Joshua.
|