User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) Sometimes when Firefox can't resolve a DNS webpage (because of a bad internet connection), it doesn't show the normal error page with the original address, but it changes the address to the error page. For example, when accessing google reader, the address in the address bar changes to about:neterror?e=dnsNotFound&u=http%3A//www.google.com/reader/view/&c=UTF-8&d=Firefox%20can't%20find%20the%20server%20at%20www.google.com. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Load a page on a bad internet connection so that the DNS reques doesn't resolve 2. Wait for the internet connection to get better 3. Click "Try again" Actual Results: The *error page* is refreshed, instead of the original page (this can be simulated by loading the about:neterror url directly) Expected Results: Clicking "Try again" refreshes the original url (opening the original URL in a new tab works). To sum it up: The "about:neterror" address should never appear in the address bar directly. I never encountered this problem until FF3.5.
Do you get the same in the Firefox safemode ? http://support.mozilla.com/en-US/kb/Safe+Mode
Matthias, I haven't been able to reproduce this bug even in normal mode (as I mentioned in the original bugreport), it just happened a few times while I had really bad internet connection (which has since been fixed somewhat). Switching to safe mode until I can reproduce the bug in normal mode seems pointless, I'm not going to browse for several months using safe mode in the hope that my connection gets bad again. I was hoping that maybe someone with the knowledge of the code would be able to find out the cause of the bug by reading my description (there probably aren't that many places in the source where this can happen). I understand that without being able to rule out the effects of extensions, this might prove to be a wild goose chase.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.