90673 - junkbuster and other non 1.1 proxies fail on some pages

Status: VERIFIED DUPLICATE of bug 38488

(Core :: Networking: HTTP, defect)

Description

[rjh]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2+) Gecko/20010711
BuildID:    200107108

When using a proxy that does not support HTTP 1.1 (e.g. Junkbuster 2.0), some
pages hang.  For example, www.cnet.com gets stuck loading forever.  It can be
stopped, but the page is then blank.

Changing the mozilla network option to only use HTTP 1.0 cures this problem.

There is probably a timeout missing, and this deserves some mention somewhere in
the help pages. It is probably also a proxy bug, since the proxy should have
errored off.

Reproducible: Always
Steps to Reproduce:
1.Make sure networking is for 1.1
2.Configure to use a proxy that does not support 1.1, e.g. Junkbuster 2.02
3.Attempt to load page www.cnet.com.  It will begin loading, go to a referenced
dynamic page, and sit loading until manually interrupted.
4.Reconfigure mozilla to use only 1.0
5.Load page www.cnet.com successfully.

Actual Results:  With 1.1 to a 1.0 only proxy server, the page load sticks in
loading until manually interrupted.

With 1.0 to a 1.0 only proxy server, the page loads correctly.

Expected Results:  An error message of some sort, and a warning in an FAQ about
this kind of proxy interaction.

Comment 1

[tor]

www.ebay.com is another page with this problem.

Comment 2

[Ashley Bischoff (blog at handcoding.com)]

Looks like a dupe of bug 38488 to me.

Comment 3

[Jens-Uwe]

bug 38488 really sounds like this one, but it was resolved WFM...

Comment 4

[Ashley Bischoff (blog at handcoding.com)]

Jens-Uwe: Right, bug 38488 does sound very similar. And, if you think they're
the same bug, then you may want to ask for bug 38488 to be re-opened if you
believe that the problem described there is still occuring.

Comment 5

[Bradley Baetz (:bbaetz)]

Whats happening is that the server is sending connection: keep-alive, showing
that it wants keep-alives

Junkbuster is stripping off the connection header, which is a hop-by-hop header
in 1.1, but still keeping the connection open. However, it identifies itsself as
 a 1.0 server. So we wait for the connection to close, but the server keeps it
open, so we never finish loading the page. If the page we fail on has a
stylesheet, then we block teh parser until that has finished, so the page will
display as blank.

Also see bug 91025 for more discussion on this.

This is a junkbuster bug - someone want to file it?

Comment 6

[tor]

A small patch to junkbuster to stop it from stripping the Connection: header -

--- ijb20/parsers.c     Fri Oct 30 22:58:47 1998
+++ ijb20.mod/parsers.c Tue Jul 17 20:18:14 2001
@@ -41,7 +41,7 @@
 
 struct parsers server_patterns[] = {
        { "set-cookie:",        11,     server_set_cookie       },
-       { "connection:",        11,     crumble                 },
+/*     { "connection:",        11,     crumble                 }, */
        { NULL,                  0,     NULL                    }
 };
 

Comment 7

[Bradley Baetz (:bbaetz)]

-> darin for when he returns.

darin - do we want to reconsider ignoring the content length?

Comment 8

[Jeremy M. Dolan]

I seem to see the 'page stuck during loading' when the page uses akamai for
their content. Also, I filed a related bug, 91771, Mozilla (when using
junkbuster) sometimes decides to get files directly, rather then use the proxy
setting. Possibly caused by the connection: thing, I'll try tor's fix.

May want to relnote this, so users can apply the patch to fix junkbuster.
Hopefully Mozilla includes all of JB's functionality soon enough to make it
unnessicary.

Comment 9

[Jeremy M. Dolan]

Also, it might be worth mentioning IE5 uses HTTP 1.0 by default through proxies.

You have to dig through the advanced prefs to find a 'Use HTTP/1.1 through
proxies' type option.

Comment 10

[Bradley Baetz (:bbaetz)]

this is already relnoted, and theres a bug somewhere on being able to set the
http version when talking to a proxy to something different to that when talking
to a normal server.

ie5 does; I was under the impression that 5.5 used 1.1 by default, although I
don't think I've tested that. It doesn't ignore the content length though, and
I'm going to talk to darin about this next week, and see what we want to do.

Comment 11

[tor]

I've seen enough things going wrong with my patched junkbuster to conclude
that the problem with jb can't be fixed that simply.  It seems that the
http 1.1 noncompliance of junkbuster is a known problem - see point 4 in
the following:

  http://www.junkbusters.com/ht/en/ijbfaq.html#idea

Comment 12

[Bradley Baetz (:bbaetz)]

The summary says that this happens with "other non 1.1 proxies". Can someone
please point me to one which shows this problem?

Comment 13

[Bradley Baetz (:bbaetz)]

The content-length problem when talking to http/1.0 servers has now been fixed
in a different way, and since noone can tell me of another proxy server with
this problem, I'm marking this a dupe of the junkbuster bug.

*** This bug has been marked as a duplicate of 38488 ***

Comment 14

[John Unruh]

Verified dupe.