From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+) Gecko/20020419 BuildID: 2002041903 It used to be that cliking on a link did not respond but this seems to be fixed now. Instead i get "document condtains no data" at random. Address does not matter. Pages DO HAVE data. reloading helps usualy. Reproducible: Sometimes Steps to Reproduce: 1. Click on a link and hope. 2. Enter an url in the location field.. Actual Results: Got error dialog. Expected Results: Browse to given location.

hm.. had that yesterday 1 or 2 times

I used to see this a lot when I was using a **** dialup link through a **** ISP with a **** transparent proxy (i.e., you tell Mozilla that you want a direct connection to the Internet, but the ISP has a proxy in the way for port 80 anyway). It would happen for me with IE 5 as well. Reporter: 1. Please describe your net connection in detail (ISP, speed, etc). 2. Does your connection use a transparent proxy? (Are you sure? I've known tech support to lie about this or simply not to know.) 3. Do you have another Internet connection you use that you could test Mozilla on? 4. Does this happen for you in other browsers?

> Reporter: > 1. Please describe your net connection in detail (ISP, speed, etc). ISP is the Estonian telephone company. ADSL connection, 128 down/64 up. proxy is cache.neti.ee: 8080 Also got zonealarm running with default settings. ISP has TCP filtering so that only responses get through. > 2. Does your connection use a transparent proxy? (Are you sure? > I've known tech support to lie about this or simply not to know.) Don't know for sure and no way to find out. > 3. Do you have another Internet connection you use that you could test > Mozilla on? I'll try not using a proxy for a while. > 4. Does this happen for you in other browsers? Never happened with ns4.77, _very_ rarely with ie5.5. Even having a **** dialup should not justify this kind of a behaviour.

Over to Networking: HTTP.

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

This is not a duplicate of 137965. In my case it has nothing to do with disconnecting. Just sometimes (about 6 out of 10) the selected link/entered address is not followed and this error dialog is displayed. Now, that i have had proxy disabled for a day, i have not seen this.

I've seen this too in builds *after* 2002041812. Also seen in builds after 2002041812: browser will get "stuck" on a link such that the stuck link always (re)loads no matter what link you are actually clicking on and 404 errors that go away after you try reloading a few times. Once I get sufficiently disgusted I go back to the 2002041812 build. Problem appears to be random.

This may be the problem: I'm using Junkbuster and it's well known that HTTP 1.1 and Junkbuster don't get along. In build 2002041812, Networking Preferences, HTTP 1.0 is selected. At some point after 2002041812 the networking preferences were changed such that protocol version can be specified separately depending on whether you have a direct connection or are using a proxy, and the proxy protocol defaults to - yep - HTTP 1.1. I'm going to set this to 1.0 and see what happens.

ok, let me explain why i think this is a duplicate of bug 137965... the summary of bug 137965 is a bit misleading... this dialog will occur whenever there is a socket level disconnect... this is not the same thing as unpluging your network connection. a socket connection may die midstream due to congestion or other problems. the server may give out have way through sending some content... whatever. without a doubt, the only cause of this dialog is a closed socket connection. if the socket connection is closed before we read any data from it, then we try to initiate a new socket connection. if that new connection fails similarly (closed before we read any data from it), then we try again up to a limit of 10 retries. after the 10th unsuccessful retry, we bail... and the user should see a "the document contains no data" error dialog. there is unfortunately a problem with the way this is implemented, because this dialog will result when the socket connection is closed halfway through the download, which is obviously incorrect. there is no other explanation for this dialog. hence the dupe. *** This bug has been marked as a duplicate of 137965 ***

Ok. Thanks four takeing the time to explain.