Closed
Bug 197343
Opened 22 years ago
Closed 19 years ago
Gopher: no error for hostname not found.
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gopherqa, Assigned: dougt)
References
()
Details
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•22 years ago
|
||
This seems to be a duplicate of the error reporting problems in bug 96887.
*** This bug has been marked as a duplicate of 96887 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
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.
Status: RESOLVED → UNCONFIRMED
QA Contact: benc → gopherqa
Resolution: DUPLICATE → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Hardware: PC → All
Comment 3•21 years ago
|
||
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•21 years ago
|
||
*** Bug 252403 has been marked as a duplicate of this bug. ***
Comment 5•19 years ago
|
||
Works on current trunk.
Status: NEW → RESOLVED
Closed: 22 years ago → 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•