Apache 2.2.2 was having problems displaying content for 'error 500'
responses (either it would not display anything, or it would display the
data output as plaintext) so i upgraded to 2.2.3 and now, at least, i am
getting apache to consistently display data but it always sends a
content-length of 0, the browser always displays the error in plaintext,
and when a script is set for the 'ErrorDocument 500' directive it will
occassionaly send only a portion of the script's output.
To reiterate: the problem is not that my script is resulting in an error
500, that is not the issue.
The problem is that, if 'ErrorDocument 500' is set to 'default' then
apache will appear to send a content-length of 0 and a content-type of
"text/plain" (either that, or that is what firefox 2.0 and 3alpha
interpret it as). Internet Explorer 6 renders the error properly but
that is likely due to the fact that it will attempt to render anything
no matter what state it is in.
When an 'ErrorDocument 500' directive is set to a cgi-script (perl,
works fine otherwise, sends a 'Status' and 'Content-Type' header (also
tried sending a 'Content-Length' header but that didn't seem to fly))
then apache will still send (or it gets read as) a content-type of
text/plain, content-length of 0 and the server will occassionally send
the full output, but, more often than not, the output will be cut off
after the 1180'th character. This will happen in both IE 6, FF 2, and
FF3alpha (minefield).
An example for the first case can be found here
http://eighty-4.com/
That should, if you are using seamonkey or firefox 2+, output the
following (displayed as plaintext, and minus the dashes) when it should
be sending it as text/html.
---------------------------------------------------------
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
[EMAIL PROTECTED] and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
</body></html>
---------------------------------------------------------
Is this a known problem, is there a known workaround for this?
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
