If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

"Connection reset by peer" error whenever leaving cnn.com

RESOLVED EXPIRED

Status

SeaMonkey
Tabbed Browser
RESOLVED EXPIRED
13 years ago
9 years ago

People

(Reporter: tajohnson, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
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

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. xyz.cnn.com).
 Generally the error message is the same all three times, but the leading
subdomain sometimes changes on the second or third try.
This worksforme with a current SeaMonkey trunk build.

Reporter, is this a problem with the Mozilla.org builds, or just the Debian
ones?  The latter typically have a bunch of patches applied to them; sometimes
those patches break things.
(Reporter)

Comment 2

13 years ago
(In reply to comment #1)
> This worksforme with a current SeaMonkey trunk build.
> 
> Reporter, is this a problem with the Mozilla.org builds, or just the Debian
> ones?  The latter typically have a bunch of patches applied to them; sometimes
> those patches break things.

I only use the Debian ones.  In any case the bug has been there for a while, I
just haven't taken the time to report it to anyone until now.  I'd encourage you
to try to duplicate it a few more times, maybe with different sites instead of
the msnbc that I used as an example.  I perhaps should have said it was
reproducible most of the time instead of always, since right now I can't
reproduce what I just submitted ten minutes ago. :)  But I do notice it
frequently...enough that I don't really use their site as a news source anymore
because it's annoying.
My point was that you should make sure to report this to Debian too.  Given the
failure to reproduce this in Mozilla.org builds so far on my part, chances are
good it's their bug.
(Reporter)

Comment 4

13 years ago
(In reply to comment #3)
> My point was that you should make sure to report this to Debian too.  Given the
> failure to reproduce this in Mozilla.org builds so far on my part, chances are
> good it's their bug.

Okay, I just reported it to them.
(Reporter)

Comment 5

13 years ago
I gave up Mozilla for Firefox, which apparently doesn't have this problem, so I
don't care about the status of this bug anymore.
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.