You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Vincent Jong <vj...@jandjgraphics.com> on 2005/12/15 03:20:32 UTC
[users@httpd] 500 Internal Server Error pages being rendered as markup
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.
Thanks for your time in this matter.
Vincent J.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Vincent Jong <vj...@jandjgraphics.com>.
Listing what I did below to apply the patch, so if I made a mistake
applying it, someone can let me know.
1. downloaded the patch to /home/some-user/temp
2. copied source tarball to /home/some-user/temp and untarred it.
3. cd /home/some-user/temp/httpd-2.2.0/modules/http
4. patch -i /home/some-user/temp/http_request.c.patch http_request.c
I then preceded to configure, make, make install. I started up the new
apache and saw the "It works!" index page of DocumentRoot and then tried
to access http://localhost/cgi-bin/test-cgi and the error page still
renders in HTML markup. The patch didn't work, so I'll file a bug after my
chiropracter appointment.
Thanks for all the help. =)
Vincent J.
On Fri, 16 Dec 2005 07:17:26 -0800, Joshua Slive <jo...@slive.ca> wrote:
> On 12/16/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
>> I'm not understanding what you mean. This was a clean install of apache
>> and after typing make install,
>> I started up this install's apache. I didn't edit the httpd.conf file.
>> All
>> the ErrorDocument lines that are in
>> httpd.conf are example lines that are commented out already. So what is
>> happening is when a user tries to access some cgi script that isn't
>> configured right, this user gets the 500 Internal Server Error page. The
>> problem with this page is that it is displayed as HTML code. There's the
>> additional line of another 500 Internal Server Error occurring when
>> trying
>> to use an ErrorDocument handling the error request. Since I've never,
>> ever
>> configured any kind of customized error documents, I wouldn't even begin
>> to know where all this error document configuration is. I prefer to use
>> apache's default configuration and error pages.
>
> (Well, before you were including a bunch of extra errordocuments in
> your config via the Include directives at the bottom, but anyway...)
>
> My appologies, you are correct. I have been able to recreate the
> problem. This may be the same as the following bug:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=36090
>
> Try the patch at the bottom of that report. If that doesn't fix the
> problem, please file a new bug report.
>
> 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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Joshua Slive <jo...@slive.ca>.
On 12/16/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
> I'm not understanding what you mean. This was a clean install of apache
> and after typing make install,
> I started up this install's apache. I didn't edit the httpd.conf file. All
> the ErrorDocument lines that are in
> httpd.conf are example lines that are commented out already. So what is
> happening is when a user tries to access some cgi script that isn't
> configured right, this user gets the 500 Internal Server Error page. The
> problem with this page is that it is displayed as HTML code. There's the
> additional line of another 500 Internal Server Error occurring when trying
> to use an ErrorDocument handling the error request. Since I've never, ever
> configured any kind of customized error documents, I wouldn't even begin
> to know where all this error document configuration is. I prefer to use
> apache's default configuration and error pages.
(Well, before you were including a bunch of extra errordocuments in
your config via the Include directives at the bottom, but anyway...)
My appologies, you are correct. I have been able to recreate the
problem. This may be the same as the following bug:
http://issues.apache.org/bugzilla/show_bug.cgi?id=36090
Try the patch at the bottom of that report. If that doesn't fix the
problem, please file a new bug report.
Joshua.
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Vincent Jong <vj...@jandjgraphics.com>.
I'm not understanding what you mean. This was a clean install of apache
and after typing make install,
I started up this install's apache. I didn't edit the httpd.conf file. All
the ErrorDocument lines that are in
httpd.conf are example lines that are commented out already. So what is
happening is when a user tries to access some cgi script that isn't
configured right, this user gets the 500 Internal Server Error page. The
problem with this page is that it is displayed as HTML code. There's the
additional line of another 500 Internal Server Error occurring when trying
to use an ErrorDocument handling the error request. Since I've never, ever
configured any kind of customized error documents, I wouldn't even begin
to know where all this error document configuration is. I prefer to use
apache's default configuration and error pages.
Thanks,
Vincent J.
On Fri, 16 Dec 2005 00:27:22 -0800, Octavian Rasnita <or...@fcc.ro>
wrote:
> Hi,
>
> From: "Vincent Jong" <vj...@jandjgraphics.com>
>
>> Well, I did a clean install of apache. I didn't change anything, started
>> up apache without any httpd.conf configuration changes and tried to
>> access
>> http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed
>> as
>> markup with the added message of:
>>
>> Additionally, a 500 Internal Server Error
>> error was encountered while trying to use an ErrorDocument to handle the
>> request.
>>
>> Basically the same problem as before.
>>
>
> Have you tried without that ErrorDocument line in httpd.conf?
> Does that line run another cgi script?
> If yes, has this script right permissions (chmod 755)?
>
> What do you mean when you say that instead of an error it prints an html
> response?
> Even when Apache prints an error in the header, it also prints a short
> html
> page in the body.
>
> Maybe conf/extra/httpd-multilang-errordoc.conf print a larger html
> content,
> and in that case some browsers will display that html content instead of
> creating its own error page based on the error code.
>
> Every response prints a response code. If you say that it prints just an
> html page instead of an error, this means that it prints another code
> than
> 500. Which is that code?
>
> Try with:
>
> telnet localhost 80
> GET http://localhost/cgi-bin/test.cgi HTTP/1.0
> <enter><enter>
>
> Teddy
>
>
> ---------------------------------------------------------------------
> 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@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
--
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Octavian Rasnita <or...@fcc.ro>.
Hi,
From: "Vincent Jong" <vj...@jandjgraphics.com>
> Well, I did a clean install of apache. I didn't change anything, started
> up apache without any httpd.conf configuration changes and tried to access
> http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed as
> markup with the added message of:
>
> Additionally, a 500 Internal Server Error
> error was encountered while trying to use an ErrorDocument to handle the
> request.
>
> Basically the same problem as before.
>
Have you tried without that ErrorDocument line in httpd.conf?
Does that line run another cgi script?
If yes, has this script right permissions (chmod 755)?
What do you mean when you say that instead of an error it prints an html
response?
Even when Apache prints an error in the header, it also prints a short html
page in the body.
Maybe conf/extra/httpd-multilang-errordoc.conf print a larger html content,
and in that case some browsers will display that html content instead of
creating its own error page based on the error code.
Every response prints a response code. If you say that it prints just an
html page instead of an error, this means that it prints another code than
500. Which is that code?
Try with:
telnet localhost 80
GET http://localhost/cgi-bin/test.cgi HTTP/1.0
<enter><enter>
Teddy
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Vincent Jong <vj...@jandjgraphics.com>.
Really, I didn't change anything.
I:
1. Stopped httpd
2. Renamed the older install directory from /usr/local/Apache2.2.X to
/usr/local/Apache2.2.X.old
3. Copied the httpd source tarball to my temp directory.
4. Untarred it and did a cd to the extracted directory.
5. ./configure --prefix=/usr/local/Apache2.2.X \
--enable-so --enable-mods-shared=all \
--enable-ssl --with-ssl
6. make
7. make install as root
8. /usr/local/Apach2.2.X/bin/apachectl start
Accessed http://localhost/cgi-bin/test-cgi and the error page rendered in
HTML code. I didn't make any changes whatsoever to this install's
httpd.conf file.
Thanks,
Vincent J.
On Fri, 16 Dec 2005 06:49:29 -0800, Joshua Slive <jo...@slive.ca> wrote:
> On 12/16/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
>> Well, I did a clean install of apache. I didn't change anything, started
>> up apache without any httpd.conf configuration changes and tried to
>> access
>> http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed
>> as
>> markup with the added message of:
>>
>> Additionally, a 500 Internal Server Error
>> error was encountered while trying to use an ErrorDocument to handle the
>> request.
>>
>> Basically the same problem as before.
>>
>> This is the configure command used:
>>
>> ./configure --prefix=/usr/local/Apache2.2.X \
>> --enable-so --enable-mods-shared=all \
>> --enable-ssl --with-ssl
>
> You're probably still using your old config files.
>
> You may indeed have found a bug here, but I am very skeptical that you
> can trigger it without *any* changes to the default config (such as
> activating the multilingual error documents).
>
> 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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Joshua Slive <jo...@slive.ca>.
On 12/16/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
> Well, I did a clean install of apache. I didn't change anything, started
> up apache without any httpd.conf configuration changes and tried to access
> http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed as
> markup with the added message of:
>
> Additionally, a 500 Internal Server Error
> error was encountered while trying to use an ErrorDocument to handle the
> request.
>
> Basically the same problem as before.
>
> This is the configure command used:
>
> ./configure --prefix=/usr/local/Apache2.2.X \
> --enable-so --enable-mods-shared=all \
> --enable-ssl --with-ssl
You're probably still using your old config files.
You may indeed have found a bug here, but I am very skeptical that you
can trigger it without *any* changes to the default config (such as
activating the multilingual error documents).
Joshua.
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Vincent Jong <vj...@jandjgraphics.com>.
Well, I did a clean install of apache. I didn't change anything, started
up apache without any httpd.conf configuration changes and tried to access
http://localhost/cgi-bin/test-cgi. The 500 internal error is displayed as
markup with the added message of:
Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the
request.
Basically the same problem as before.
This is the configure command used:
./configure --prefix=/usr/local/Apache2.2.X \
--enable-so --enable-mods-shared=all \
--enable-ssl --with-ssl
Thanks,
Vincent J.
On Thu, 15 Dec 2005 17:10:58 -0800, Joshua Slive <js...@gmail.com> wrote:
> On 12/15/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
>
>> 16. uncommented 'Include conf/extra/httpd-mpm.conf', 'Include
>> conf/extra/httpd-multilang-errordoc.conf', 'Include
>> conf/extra/httpd-autoindex.conf', 'Include
>> conf/extra/httpd-languages.conf', and 'Include
>> conf/extra/httpd-ssl.conf'
>> lines - By default all the include lines were commented
>
> Well httpd-multilang-errordoc.conf is certainly important here. The
> problem will likely go away if you comment that out. There are a
> bunch of ErrorDocument directives in there. Most likely they are
> interacting poorly with some other access restriction that you have
> added. Or you are missing some module required by those settings.
>
> 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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Joshua Slive <js...@gmail.com>.
On 12/15/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
> 16. uncommented 'Include conf/extra/httpd-mpm.conf', 'Include
> conf/extra/httpd-multilang-errordoc.conf', 'Include
> conf/extra/httpd-autoindex.conf', 'Include
> conf/extra/httpd-languages.conf', and 'Include conf/extra/httpd-ssl.conf'
> lines - By default all the include lines were commented
Well httpd-multilang-errordoc.conf is certainly important here. The
problem will likely go away if you comment that out. There are a
bunch of ErrorDocument directives in there. Most likely they are
interacting poorly with some other access restriction that you have
added. Or you are missing some module required by those settings.
Joshua.
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Vincent Jong <vj...@jandjgraphics.com>.
I did set up 2 .htaccess directories in the document root, but I don't
know why this would cause this issue I'm seeing.
But again, I've also successfully reproduced the problem with the original
httpd.conf files on 2 different machines, which makes this extremely
wierd, since there aren't any .htaccess directories specified in the
original httpd.conf.
Things I've changed in my httpd.conf file:
1. admin email address
2. server name
3. user nobody
4. group eng
5. ServerTokens Full
6. ServerSignature On
7. Options in DocumentRoot's <Directory> directive
8. added <Directory> directive for .htaccess protected directory in
DocumentRoot
9. added another <Directory> directive for .htaccess protected directory
in DocumentRoot
10. set up UserDir directories and added <Directory> directives for user
directories
11. in <IfModule dir_module>, added values to DirectoryIndex directive
12. in <IfModule mime_module>, uncommented 'AddEncoding x-compress .Z' and
'AddEncoding x-gzip .gz .tgz' lines
13. in <IfModule mime_module>, uncommented 'AddHandler cgi-script .cgi'
line and added '.pl' and '.py' to that line
14. in <IfModule mime_module>, uncommented 'AddHandler type-map var',
AddType text/html .shtml', and 'AddOutputFilter INCLUDES .shtml' lines
15. in <IfModule mime_module>, added 'AddHandler php5-script .php',
'AddType text/html .php', and 'AddType application/x-httpd-php-source
.phps' lines
16. uncommented 'Include conf/extra/httpd-mpm.conf', 'Include
conf/extra/httpd-multilang-errordoc.conf', 'Include
conf/extra/httpd-autoindex.conf', 'Include
conf/extra/httpd-languages.conf', and 'Include conf/extra/httpd-ssl.conf'
lines - By default all the include lines were commented
I've also made changes to the httpd-ssl.conf file - admin email address,
server name, and <Location> directive for subversion.
I'm really not sure where to go from here since I've been able to
reproduce this on 2 different machines with both my altered httpd.conf and
the original httpd.conf files and you are not able to reproduce this.
Thanks,
Vincent J.
On Thu, 15 Dec 2005 16:16:37 -0800, Joshua Slive <jo...@slive.ca> wrote:
> On 12/15/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
>> I also just noticed when reading the rendered page more correctly:
>>
>> Additionally, a 500 Internal Server Error
>> error 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...
>
> I'm having a hard time believing this statement. Have you checked any
> config file that may be Include'd in httpd.conf or any .htaccess file?
>
> 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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Joshua Slive <jo...@slive.ca>.
On 12/15/05, Vincent Jong <vj...@jandjgraphics.com> wrote:
> I also just noticed when reading the rendered page more correctly:
>
> Additionally, a 500 Internal Server Error
> error 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...
I'm having a hard time believing this statement. Have you checked any
config file that may be Include'd in httpd.conf or any .htaccess file?
Joshua.
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Vincent Jong <vj...@jandjgraphics.com>.
I also just noticed when reading the rendered page more correctly:
Additionally, a 500 Internal Server Error
error 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 <vj...@jandjgraphics.com>
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 <js...@gmail.com>
> wrote:
>
>> On 12/14/05, Vincent Jong <vj...@jandjgraphics.com> 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.
>
>
>
--
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Vincent Jong <vj...@jandjgraphics.com>.
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 <js...@gmail.com> wrote:
> On 12/14/05, Vincent Jong <vj...@jandjgraphics.com> 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.
--
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] 500 Internal Server Error pages being rendered as markup
Posted by Joshua Slive <js...@gmail.com>.
On 12/14/05, Vincent Jong <vj...@jandjgraphics.com> 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.