Open Bug 441764 Opened 17 years ago Updated 3 years ago

message is unclear when trying to go to a domain with an invalid URL

Categories

(Firefox :: General, defect)

defect

Tracking

()

People

(Reporter: matt, Unassigned)

Details

On some systems a domain name which starts or ends with a "-" will get an error when attempting to resolve the name even though the DNS server will happily resolve it. The "Address Not Found" page should include a note on this if the domain name might trigger this problem.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Nevermind, not a duplicate. You just want it to tell users why it's failing.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
A leading "-" or a "-" at the end are just invalid (not allowed) and that means that such a name should not exists at all. Do you want to explain every case for an invalid URL that might work with some OS/DNS combination ?
I think the point is that while it is invalid, that doesn't mean it isn't occasionally done anyway. Windows basically just ignores the spec and due to market share: bug->feature. User confusion could be avoided if the error message was more informative. Personally, I think the problem here is that the error message is "Address Not Found" and not an "Invalid URL" error of some type. It shouldn't try to see if it works; it should just know and stop from the start. Otherwise, you get this inconsistent behavior across multiple OSes. However, that being said, I don't think it's that big of a deal. My guess is that someone will come along and WONTFIX this.
Well, first off this is probably in the wrong component, since the exact text is up to the app, not really a docshell thing, last I checked.
Status: REOPENED → NEW
Component: Embedding: Docshell → General
Product: Core → Firefox
QA Contact: docshell → general
Version: unspecified → Trunk
Severity: enhancement → trivial
Summary: Address Not Found: note domain names with starting/ending dashes → message is unclear when trying to go to a domain with an invalid URL
Severity: trivial → S4
You need to log in before you can comment on or make changes to this bug.