Closed Bug 160047 Opened 22 years ago Closed 22 years ago

"Connection refused" sheet comes down for every instance

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: huskerdu, Assigned: sfraser_bugs)

References

Details

Attachments

(2 files)

When ad servers and such are pointed to 127.0.0.1 in /etc/hosts or NetInfo,
every time Chimera tries to connect to one of those hosts, it drops down a sheet
saying it cannot connect to it, making you click OK or hit enter every time. 
This makes navigation very frustrating.  Neither IE nor OmniWeb does this, only
Chimera and Mozilla.
Severity: normal → major
Attached image an example of the sheet
This happens every time one of these hostnames comes up.  For one page, I might
have to go through three or four of these!
Ken, if you do that, you'll need to be running your web server so the
redirection has something to talk to.

(Or, this could also be Chimera's bug 28586.)
Summary: "Connection refused " sheet comes down for every instance → "Connection refused" sheet comes down for every instance
Yeah, it does look like bug 28586.  I saw mention of a patch for Mozilla that
will change these dialogs to error messages.  Will this be available for Chimera?

Thanks.
Localhost is only a very narrow case of this bug though.  No matter what the
host, it still doesn't make sense to tell the user, say, 10 times that the host
is down, if there are 10 images.

This might happen if the host serving the pages points to an images server, for
instance.
May I please ask if this is anywhere near being worked on?  I love Chimera, but this is really the only thing that constantly annoys me.

Thanks.

*** Bug 173400 has been marked as a duplicate of this bug. ***
Darin: is there a way the embedder can tell if the 'connection refused' dialog
is being shown for the main page, or some other element on the page?
i thought adam lock said he fixed this on the mozilla trunk.  perhaps chimera
just needs the same fix applied to its branch.
Taking
Assignee: saari → sfraser
Patch checked in (patch should *not* be merged to trunk).
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
I just tried the Jan. 01 build and couldn't be happier!  Thank you so much, guys!

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: