96365 - An alert about connection refusal pops up with every click at www.wwf.com

Status: VERIFIED FIXED

(Tech Evangelism Graveyard :: English US, defect)

Description

[elaineking]

From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en]C-AOL  (Win98; U)
BuildID:    20010820

In the Mozilla/Netscape 6 browser, one of the top 500, www.wwf.com shows an 
alert 3-7 times before each page will finally render.  The alert reads, "The 
connection was refused when attempting to connect to cs.wwf.com."  One must 
click OK repeatedly until the alert stops. This alert does not appear on IE or 
Netscape 4.x

Reproducible: Always
Steps to Reproduce:
1.go to www.wwf.com
2.click through the alerts until the page is stable
3. click on any link, then click through the alert until the page is stable.  it 
just keeps going and going...

Comment 1

[Jesse Ruderman]

The WWF's ads aren't appearing in Internet Explorer either, so I'm sure they're 
aware of the problem ;)

I'd say this is a dup of bug 28586, "Should use error page, not dialog, for 
inaccessible pages".

Comment 2

[Paul Roub]

Is this really a dup, though?  I think we're talking here about IFRAMEs that
don't load -- I was going to submit the same problem as a feature request.

Essentially, the entire page loads happily, but the ads don't -- in my case,
because I have many ad URLs blocked, and I have to endure a multitude of alert
boxes about the ads.  

So the feature request version would be: please give me a preference setting to
keep silent about failed IFRAME loads.

Comment 3

[Bob Clary [:bc] (inactive)]

I would say this is a dupe of the RFE to remove the alerts when failing to
connect to a page. That would cover the iframe issue as well. As far as your
blocking of the offending ad sites, I think that if you map the offending url to
a 127.0.0.1 page you could live with this stuff...

As far as the original bug report, the page loads fine now so I will mark as fixed.

Comment 4

[Paul Roub]

FYI - The URLs in question *were* mapped to 127.0.0.1.  The messages didn't go
away until I added a local web server whose job was to 404 everything.

Does the 127.0.0.1 behavior merit a separate bug report?

Comment 5

[Bob Clary [:bc] (inactive)]

No, I think the need to actually serve up the 404 page is actually covered in
the other bug report. I agree it is a pain to have to deal with these alerts.
Perhaps if we voted for the bug...

Comment 6

[Brant Gurganus]

Verified
2002030908/WinXP