Open Bug 998606 Opened 7 years ago Updated 5 years ago
Investigate issues with correcting already-loading URLs in case of slow DNS/server response (error page for unrequestable/cancelled request replaces / loads instead of corrected URL)
Steps to Reproduce 1. Have a bookmark with a valid URL which is easilly accessible through Firefox UI. 2. Type the following in the location bar excluding the double quotations - "test.test", press enter and immediately press the bookmark link. Actual Results Firefox loads the webpage that is navigated by the bookmark. A moment later, Firefox gives an error "Firefox can't find the server at www.test.test.". Expected Results I invite the community to decide upon the valid behaviour. For example, Firefox could forget the previous URL and just keep the web page that the user is currently working with. Sidenote: As an example, a user with an ADSL router with manual connection could find this situation annoying when; 1. Without realizing that there is internet connection, the user tries to navigate to a website. 2. Before Firefox could give out an error, the user suddenly realizes that there is no internet and navigates to the router's page on the same tab. 3. There is a chance for the user to get an error before pressing "Connect" in the router's page.
I believe this is a UI problem, not a networking one.
Component: Networking → General
Product: Core → Firefox
Confirming per the group of people reporting this, since at least 28. All on Windows (7 and 8). I can't reproduce with "test.test" - my DNS provider fails much too quickly. However, my local windows 8 machine has no webserver running locally, but the port is also not closed, so I can reproduce with: 1. try to load "localhost" (waits a long time before giving up) 2. Immediately click a bookmark in the bookmarks toolbar. This will always show the error page for localhost ("unable to connect"). I have no problem believing we can hit this case for slow DNS responses, too. Either way, this is wrong, and we should fix it. The first step will be investigating whether Josh's comment #1 is correct (I suspect it is, but either way, someone will need to actually look). CC'ing Mike because this is on the beautiful intersection between UI, docshell and actual requests... :-)
Status: UNCONFIRMED → NEW
Points: --- → 13
Ever confirmed: true
See Also: 997154 →
Summary: Firefox gives Server Not Found error for the previous request → Investigate issues with correcting already-loading URLs in case of slow DNS/server response (error page for unrequestable/cancelled request replaces / loads instead of corrected URL)
You need to log in before you can comment on or make changes to this bug.