283592 - No error message/response if a webserver fails to respond correctly after accepting a connection.

Status: RESOLVED INVALID

(Core :: Networking, defect)

Description

[Stephen Jayna]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050109 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050109 Firefox/1.0

No error message/response is given if a connection is opened successfully and
the webserver (apache) crashes during delivery subsequently closing the connection.

The webserver will essentially closes the connection without writing any output.

Reproducible: Always

Steps to Reproduce:
1. Go to any working web page. eg. http://www.google.com
2. Go to a page where the webserver crashes while responding (in the same
window/tab). eg. http://www.everita.com/anon/bug


Actual Results:  
You are presented with the initial page you visited, there is no warning that
you didn't recieve a correct response from the second page.

Expected Results:  
It should have displayed an error that indicated that the webserver failed to
return a valid response, NOT the previous page you visited.

A sample telnet connection to an Apache 1.3.20 (Unix) webserver that crashes
(segs) while responding.

Connected to blackbox.projectuno.com (192.168.42.7).
Escape character is '^]'.
GET /anon/bug HTTP/1.1
Host: www.everita.com

Connection closed by foreign host.

Comment 1

[Andrew Schultz]

this was fixed a long time ago (see bug 90976), but it's been rebroken for a
while (since at least 1.4)

Comment 2

[Boris Zbarsky [:bzbarsky]]

A build from Oct 2001 retries a bunch of times but then finally does the same as
a current build -- nothing.

Darin, what error does HTTP return for this case in OnStopRequest?  It sounds
like docshell needs to report it, whatever it is.

Comment 3

[Darin Fisher]

-> default owner

Comment 4

[Patrick McManus [:mcmanus]]

to http, this is a 0 byte response that we treat as an empty 0.9 result..