197343 - Gopher: no error for hostname not found.

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[gopherqa]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5
Build Identifier: 

STEPS:
go to gopher URL that has bad hostname:

gopher://gopher.mozilla.org

EXPECTED:
DNS error message "hostname not found"

OBSERVED:
Mozilla 1.3b displays URL w/ empty directory.
Phoenix 0.5 displays "resolving status.


Reproducible: Always

Steps to Reproduce:

Comment 1

[Dan Mellem]

This seems to be a duplicate of the error reporting problems in bug 96887.

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

Comment 2

[benc]

REOPEN: DNS errors are not the same as connection refused.

Connection refused is when a system is up (responds to ping), but is not running
the right server. For example, Almost every web server on the internet is not
running gopher, and should return this error.

DNS "not found" means there is no DNS "label" for the hostname requested.

Comment 3

[Bradley Baetz (:bbaetz)]

This used to work, but I haven't played with goperh for a while, so its possible
that it missed some API change somewhere (probably to do with interface
requestors and the prompt service)

Comment 4

[Josh Birnbaum]

*** Bug 252403 has been marked as a duplicate of this bug. ***

Comment 5

[Eli Friedman]

Works on current trunk.