181476 - DNS: Site Not Found - Offer to do Host -a siteurl

Status: RESOLVED WORKSFORME

(Core :: Networking, enhancement)

Description

[Stephane Moureau]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021119 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021119 Chimera/0.6+

Sometimes it seems OS X has problem to find some sites, you must try 2 or 3
times before reaching them because the DNS lookup has problem (Apple knows about
that since 10.0.0), so it will probably not disappear very soon.
What about offering in the Alert sheet to make a "host -a siteurl" and try again
to reload that site. A button with something like "Try to resolve the site
address and load it again"... in a shorter version or with a small explanation
static text field.
I add that problem with several sites and since I've done that in Terminal with
those sites, the Not Found problem has disappeared.

Reproducible: Always

Steps to Reproduce:




host -a tip was found on Chimeraboard.

Comment 1

[Steve Smart]

Wouldn't it make more sense if we just tried this without requiring any user
intervention, before we brought up a site not found? What reason would there be
for the user to not want to try and resolve the site?

Comment 2

[Stephane Moureau]

I thought to that also (no sheet) but I don't think it will be good because the
user might lose patience and try again if he is not aware that a second try is made.

Perhaps the sheet could appear saying something like "Please wait, trying to
resolve that url a second time" and disappear automatically if it's ok.
If it's not the error is changed to what we receive now.

Or adding a message in the status bar, but the problem here is that sometimes
the status bar is not visible.

Comment 3

[Sören 'Chucker' Kuklau (gone)]

Too complicated. How about we just add a "Try again" button and rename "OK" to
"Cancel"?

As to the resolving issues, I only experience that when switching from one
network to another (on a laptop). Restarting Chimera usually fixes it.

Comment 4

[Simon Fraser [no longer active]]

Is this still an issue in 10.2.3? Suggest WONTFIX.

Comment 5

[Stephane Moureau]

Since ~10 days several users are complaining that there is more and more
"Document contains no data" error.
I have also the problem and I'm wondering if it's not worse since 10.2.3.
I have it almost 1/4 clicks on versiontracker.com (I'm in Belgium)
I have made a lot of tests (clean cache, reboot, relaunch, various prefs
settings, etc) nothing seems to make a difference.
The host -a does not seems to be so effective to solve that problem neither.
I'll try to make new tests with other browsers to see if it's really Chimera
that's involved.

Comment 6

[Simon Fraser [no longer active]]

> Since ~10 days several users are complaining that there is more and more
> "Document contains no data" error.

How many of those users have pipelining enabled (which we know is broken)?

Comment 7

[Stephane Moureau]

Probably most of them have pipelining enabled, according to poll.

Comment 8

[Mike Pinkerton (not reading bugmail)]

mozilla issue

Comment 9

[Mike Pinkerton (not reading bugmail)]

really

Comment 10

[Matthias Versen [:Matti]]

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

Comment 11

[benc]

REOPEN:

Although this bug would use error pages, it is not the same as the other bug.

This bug is saying that we should get users to type (either manually, or via a
URL    (and likely a new URLs scheme)) something that will workaround some type
of DNS bug in only Mac OS X.

Absent more specific data, I agree w/ Simon's WONTFIX suggestion.

I think the problem described is something to do w/ layers of caching between
the resolver and the application (lookupd?). If there is an OS bug, then the OS
vendor needs to fix it. I cannot recall a large number of complaints about this
showing up in bugzilla, so I'm not convinced we need to add more stuff to the
error dialogs for this condition.

Comment 12

[Matthias Versen [:Matti]]

I disagree with reopening but you are the QA.
The bug should be already fixed in OS X and we would have more reports if this
would be a real problem in recent OS X builds.

The error pages would be an easy way to solve this because you can simple click
on retry

Comment 13

[Darin Fisher]

resolving WORKSFORME... 

i think this bug should be fixed now.  i'd like to hear from the original
reporter of the problem.  if this bug is still somehow a problem with recent
mozilla builds, then i agree we should re-address it.  but, at the moment, this
looks like something that should be "ok" now.