Closed Bug 219528 Opened 21 years ago Closed 21 years ago

VeriSign SiteFinder replaces selected Smart Browsing Internet Keyword handler

Categories

(Core :: Networking, enhancement)

enhancement
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 219464

People

(Reporter: bgallia, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 VeriSign SiteFinder breaks some of the functionality of Smart Browsing. I would like to suggest adding an "Domain existence verification" option to Smart Browsing. When enabled, Mozilla should do an NS lookup on the domain first before doing an A/CNAME lookup. While an A/CNAME lookup for name-with-typo.com will be redirected to SiteFinder, an NS lookup on name-with-typo.com will reveal an NXDOMAIN response allowing Mozilla Smart Browsing to act accordingly. Reproducible: Always Steps to Reproduce: 1.Turn on Internet Keywords and Domain Guessing 2.Type a signal mis-spelled word or give a full URL to a mis-spelled domain under .net or .com 3.Take note that the Smart Browsing Internet Keyword functionality is no longer provided Actual Results: Mis-spelled domains now result in VeriSign SiteFinder instead of the choosen handler for Internet Keyword. Expected Results: Confirmed the existence of the domain via lookup for an NS record and for an NXDOMAIN produced results from the choosen handler for Internet Keyword.
Summary: VeriSign SiteFinder breaks Smart Browsing → VeriSign SiteFinder replaces selected Smart Browsing Internet Keyword
Summary: VeriSign SiteFinder replaces selected Smart Browsing Internet Keyword → VeriSign SiteFinder replaces selected Smart Browsing Internet Keyword handler
*** This bug has been marked as a duplicate of 219464 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
V dupe.
Status: RESOLVED → VERIFIED
Component: Browser-General → Networking
QA Contact: general → benc
You need to log in before you can comment on or make changes to this bug.