I also just noticed when reading the rendered page more correctly: Additionally, a 500 Internal Server Errorerror was encountered while trying to use an ErrorDocument to handle the request.
I've looked in the error log and it doesn't look like anything is funny in there.
[Thu Dec 15 15:00:59 2005] [notice] Apache/2.2.0 (Unix) mod_ssl/2.2.0 OpenSSL/0.9.7a DAV/2 configured -- resuming normal operations [Thu Dec 15 15:01:01 2005] [error] [client 127.0.0.1] (13)Permission denied: exec of '/usr/local/Apache2.2.X/cgi-bin/test-cgi' failed [Thu Dec 15 15:01:01 2005] [error] [client 127.0.0.1] Premature end of script headers: test-cgi
It looks like there's an error somewhere in the configuration file, but I haven't done any changes regarding error documents...
Thanks, Vincent J.On Thu, 15 Dec 2005 14:59:38 -0800, Vincent Jong <vjong@xxxxxxxxxxxxxxxxx> wrote:
Yeah. I did that already on my home system and the error page is still being displayed as markup. I just tried it on my server at work, which is also running version 2.2.0, and the same problem occurs when using either my altered httpd.conf or the original httpd.conf file. I'm basically, just accessing one of the default cgi-scripts in cgi-bin that has the permissions 644. The URL I'm trying out is http://localhost/cgi-bin/test-cgi.Thanks, Vincent J.On Thu, 15 Dec 2005 10:18:30 -0800, Joshua Slive <jslive@xxxxxxxxx> wrote: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 theproblem still existed with the original httpd.conf file. I guess, myquestions 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 andthere wasn't much help for me there as I tried to get someone else toreconfirm 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 thescript.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.
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|