155238 - pipelining: problem with premature connection close

Status: RESOLVED WORKSFORME

(Core :: Networking: HTTP, defect)

Description

[Jan Bobrowski]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
BuildID:    2002063012

When server decides to close connection while there are outstanding pipelined
requests, browser keeps showing "Transfering data...". I seems that it doesn't
reissues requests on new connection

Request1
Request2
Request3
 -> Response1 (keep-alive)
 -> Response2 (close)
 (connection closed)


Reproducible: Always
Steps to Reproduce:
Sorry. This happened when I tested my experimental server supporting pipelining.

Expected Results:  Send unresponded request again on another connection.

Comment 1

[benc]

-> HTTP

Comment 2

[Boris 'pi' Piwinger]

Is this still a problem in 1.1 or later?

pi

Comment 3

[Jan Bobrowski]

Yes and no. I just checked it using Mozilla 1.1 (win):
The browser reports "Document done", but broken images are shown. It's buggy
behaviour. If the server responds with "Connection: Close", other requests on
the same connection should be treat as never send (cause server explicitly
reported that they were sent on closed connection). Pipelined requests are sent
with the HOPE that they're correct (if connection is in closed state, client is
not allowed to send anything), if server decides that they are not, they should
be send again.

Comment 4

[Thomas]

Is this still a problem with Mozilla 1.7?

Comment 5

[Thomas]

Jan, does this only apply to Windows 98? (is your server Windows 98 or your
workstation?)
Have you tried this yet with Mozilla 1.7 final (or later)?

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Darin Fisher]

I believe that we have code to explicitly handle this case now.  The bug is old
enough that it is likely to have been fixed in more recent versions of the code.
 I don't know the bug to dupe this against, so I'm just going to mark this bug
WORKSFORME.  Please reopen this bug report if the problem can still be
reproduced using a more recent version of Mozilla or Firefox.  Thanks!