Bug#412580: Clarification for solution
I can't tell for sure whether Stefan's comment (posted today) means the intent is that the patch posted by Tim on the 28th will be applied, or if the latest version of Apache will really be used. I want to assume the latter, based on the phrase "the latest version of apache2 ..." but I thought it would be prudent to check to be absolutely certain. If the former, please look at http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/generators/mod_cgi.c?revision=541990&view=markup which is the head of the svn trunk for mod_cgi.c, with a slightly less simple fix for the problem (with a substantial comment documenting why it's being done this way). -- Bob Kline http://www.rksystems.com mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412580: Info received
Forwarded: 412580 [EMAIL PROTECTED] Tag: 412580 patch upstream etch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412580: (no subject)
forwarded 412580 [EMAIL PROTECTED] tag 412580 patch upstream etch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412580: [Debian bug #412580] Apache reporting incorrect header values for error 500 documents
I have gone back and confirmed that this was not broken on Sarge. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#412580: Apache reporting incorrect header values for error 500 documents
Package: apache2.2-common
Version: 2.2.3-3.3
Severity: important
The version of Apache which ships with Etch sends back the document
specified in the ErrorDocument directive with a Content-length header of
0 and a Content-type header with a value other than text/html, which
causes the browser to either display an empty document or offer to
download the (empty) document to the file system on the client machine.
Apache on earlier versions of Debian did not exhibit this behavior,
though I'm not sure when it was introduced (hadn't used Debian for a
while, and I'm in the process of building a new Debian server).
This bug prevents the server from informing the user what went wrong and
whom to contact when a script fails unexpectedly.
This is probably related to Apache bug 39710
(http://issues.apache.org/bugzilla/show_bug.cgi?id=39710).
To reproduce:
1. Install the following script as barf.py in the /cgi-bin directory:
#!/usr/bin/python
raise Exception("barfing")
2. Make sure the ErrorDocument 500 directive points to a real document.
3. Invoke the URL for the script:
$ curl -i http://localhost/cgi-bin/barf.py
HTTP/1.1 500 Internal Server Error
Date: Mon, 26 Feb 2007 21:16:17 GMT
Server: Apache/2.2.3 (Debian)
Content-Length: 0
Connection: close
Content-Type: text/x-python
On all my other servers, Content-length is non-zero and Content-type is
text/html.
--
Bob Kline
http://www.rksystems.com
mailto:[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
