Bug#151645: mozilla-browser: HTTP/1.1 Pipelining gets confused.

[Thomas Roessler]

I don't remember having seen the problem with any more recent
Mozilla; since I'm not currently using Debian, though, I couldn't
tell.

I'd suggest you consider this bug closed unless somebody else
reports it again.
-- 
Thomas Roessler   <roessler at does-not-exist.org>






On 2006-12-26 13:53:48 +0100, Andreas Metzler wrote:
> From: Andreas Metzler <ametzler at downhill.at.eu.org>
> To: Thomas Roessler <roessler at does-not-exist.org>
> Cc: 151645 at bugs.debian.org
> Date: Tue, 26 Dec 2006 13:53:48 +0100
> Subject: Re: mozilla-browser: HTTP/1.1 Pipelining gets confused.
> Reply-To: 151645 at bugs.debian.org
> X-Spam-Level: 
> 
> On 2002-07-02 Thomas Roessler <roessler at sobolev.does-not-exist.org> wrote:
> > Package: mozilla-browser
> > Version: 2:1.0.0-0.woody.1
> > Severity: normal
> 
> > It seems like HTTP pipelining occasionally gets confused, and out of
> > synch with the server's answers.  Mozilla then offers me to save the
> > web page in question as an application/x-httpd-php3 file (the
> > content type is apparently determined from the file name); that file
> > contains the actual HTTP header, and part of the server's response
> > (like "1 200", cut off from "HTTP/1.1 200").
> 
> > To reproduce activate persistent connections and pipelining, and
> > stress-test it a bit.  (For instance on a site which opens many
> > sub-windows.) If needed to debug this further, I have a packet trace
> > of a session where this happened available.  As far as I can see it,
> > the dialogue between Mozilla and the server was flawless on the
> > wire.
> [...]
> 
> Can you still reproduce this with iceape (or even mozilla 1.7.x)?
> cu andreas
> 
>