1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#265525: mozilla: "Connection reset by peer" error

    From Troy A. Johnson@1:229/2 to All on Fri Aug 13 17:10:09 2004
    From: [email protected]

    Package: mozilla
    Version: 1.7.2-2

    User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040810 Debian/1.7.2-2
    Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040810 Debian/1.7.2-2

    I have reported this to bugzilla.mozilla.org and they suggested reporting
    to Debian: http://bugzilla.mozilla.org/show_bug.cgi?id=255472

    For the past few months, whenever visiting http://www.cnn.com in a tab of
    the browser, if I then change the tab's URL to point to another web site
    and press enter, I get a message like the following: "TCP connection to 'cl.cnn.com' failed: Connection reset by peer." Note that while getting
    that message the URL for the tab is still what I changed it to, say http://www.msnbc.com for example. If I continue to try reloading the new
    URL, it typically takes three tries before I reach the new page. I think
    this is a Mozilla bug because I'm not following a link from CNN, I'm
    simply manually changing the URL for the tab and pressing enter. Mozilla should load the page using the new URL, but instead continues to contact
    CNN's web site several more times, only switching to load the new site on
    the third try.

    Reproducible: Always
    Steps to Reproduce:
    1. Goto http://www.cnn.com
    2. Open a few articles in tabs using middle mouse button.
    3. View one of the tabs.
    4. Change the tab's URL to some other web site, say http://www.msnbc.com
    5. Press enter.
    6. Receive a "TCP connection to 'cl.cnn.com' failed: Connection reset by
    peer." error message.
    7. Click reload or click on the URL text and press enter again.
    8. Get the error message again.
    9. Repeat steps 7 and 8 to get the message a third time.
    10. Reload yet again and actually make it to the new site.

    Actual Results:
    I received an error message instead of seeing the web site I wanted to
    see.

    Expected Results:
    Mozilla should load the new URL in the tab and not contact the CNN site at
    all.

    Occasionally the "TCP connection to 'cl.cnn.com' failed: Connection reset
    by peer." error message will have a different leading subdomain (e.g. i.cnn.com). Generally the error message is the same all three times,
    but the leading subdomain sometimes changes on the second or third try.


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Takuo KITAME@1:229/2 to All on Fri Aug 13 17:40:04 2004
    From: [email protected]

    tag 255472 unreproducible
    stop

    Works for me.
    Isn't it just network problem?



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Troy A. Johnson@1:229/2 to Takuo KITAME on Fri Aug 13 18:00:13 2004
    From: [email protected]

    On Sat, 14 Aug 2004, Takuo KITAME wrote:

    tag 255472 unreproducible
    stop

    Works for me.
    Isn't it just network problem?

    No, it's not a network problem. Here is a simplified explanation of
    what happens.

    1) Use a tab to view web site A.
    2) Change URL of tab to web site B and press enter.
    3) Mozilla reports a TCP connection reset error **for web site A.**

    Step 2 should not cause Mozilla to contact site A at all.

    Either
    i) Mozilla continues contacting site A and should not be doing so, or
    ii) Mozilla does contact site B but reports a network error for site A
    instead of reporting it for site B.

    It just so happens the only time that I've experienced this is when site A
    is CNN's web site, but I don't see how it can be their problem and not a Mozilla problem because their site should not be able to cause Mozilla to continue to contact their site once I've changed the URL to something completely different.

    -Troy


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Takuo KITAME@1:229/2 to All on Fri Aug 13 20:50:14 2004
    From: [email protected]

    2004-08-13 ($B6b(B) $B$N(B 10:34 -0500 $B$K(B Troy A. Johnson $B$5$s$O=q$-$^$7$?(B:
    On Sat, 14 Aug 2004, Takuo KITAME wrote:

    tag 255472 unreproducible
    stop

    Works for me.
    Isn't it just network problem?

    No, it's not a network problem. Here is a simplified explanation of
    what happens.

    1) Use a tab to view web site A.
    2) Change URL of tab to web site B and press enter.
    3) Mozilla reports a TCP connection reset error **for web site A.**

    Step 2 should not cause Mozilla to contact site A at all.

    Either
    i) Mozilla continues contacting site A and should not be doing so, or
    ii) Mozilla does contact site B but reports a network error for site A
    instead of reporting it for site B.

    It just so happens the only time that I've experienced this is when site A
    is CNN's web site, but I don't see how it can be their problem and not a Mozilla problem because their site should not be able to cause Mozilla to continue to contact their site once I've changed the URL to something completely different.

    Have you installed tab-extension package?




    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Troy A. Johnson@1:229/2 to Takuo KITAME on Fri Aug 13 21:00:22 2004
    From: [email protected]

    On Sat, 14 Aug 2004, Takuo KITAME wrote:

    2004-08-13 (��) �� 10:34 -0500 �� Troy A. Johnson ����Ͻ񤭤ޤ���:
    On Sat, 14 Aug 2004, Takuo KITAME wrote:

    tag 255472 unreproducible
    stop

    Works for me.
    Isn't it just network problem?

    No, it's not a network problem. Here is a simplified explanation of
    what happens.

    1) Use a tab to view web site A.
    2) Change URL of tab to web site B and press enter.
    3) Mozilla reports a TCP connection reset error **for web site A.**

    Step 2 should not cause Mozilla to contact site A at all.

    Either
    i) Mozilla continues contacting site A and should not be doing so, or
    ii) Mozilla does contact site B but reports a network error for site A
    instead of reporting it for site B.

    It just so happens the only time that I've experienced this is when site A is CNN's web site, but I don't see how it can be their problem and not a Mozilla problem because their site should not be able to cause Mozilla to continue to contact their site once I've changed the URL to something completely different.

    Have you installed tab-extension package?

    No. This is the first I've heard of it. I just did a Google search for
    it and it looks useful, but I've never tried using it.

    -Troy

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)