User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 If domain guessing is switched on, and someone mistypes the protocol part at the start of the URL, for example: http//:www.hotmail.com/ instead of http://www.hotmail.com Domain guessing will take them to www.http.com, which will take them to a site that offers a solution to disable pop-ups and all kinds of things (and no, it's not a Mozilla download mirror :-)). Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: I'm not sure what would be the most user-friendly solution to this problem. So far I've thought of: (with domain guessing on) a) on detection of a bad protocol, Mozilla should strip the protocol section and take its chances on what's left; b) Mozilla should send the user to an explanatory error page that says you really ought to learn to type the protocol section of the URL properly c) Mozilla should produce the same error as it would with domain guessing off, being <whatever> is not a registered protocol. Though that could confuse people as http is a registered protocol, just they typed the bit after wrong. I prefer solution b, but then no-one seems to like my idea of producing explanatory error pages in situations where short error message windows can serve to confuse the clueless more. I'll write the content of the explanatory error pages if that's what people find to be the most tedious part.
Hmm, my last paragraph came off a bit terse, I didn't mean it to sound like that. I think I could do a good job at writing a decent explanation that most users could understand of how their intended navigation might have erred.
The problem is telling apart "http//:www.hotmail.com/" and "http/www.hotmail.com" and "mozilla.org/foo.html"
RECOMMEND: WONTFIX We get occasional requests to fix "this or that extremely unlikely typo". If you factor in the need to exhaustively test combinations and deal with regressions, it probably is not worth doing.
Assignee: general → location-bar
Component: Browser-General → Location Bar
QA Contact: general → benc
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
REOPEN to wontifx.
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago → 13 years ago
Resolution: --- → WONTFIX
Summary: domain guessing and protocol issue → Domain Guessing: avoid guessing on protocol (URL scheme)
You need to log in before you can comment on or make changes to this bug.