Closed Bug 595015 Opened 15 years ago Closed 14 years ago

FF reports a link as broken, but IE8 can usually access it

Categories

(Firefox :: General, defect)

3.6 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jddbusiness, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729) I am almost ready to uninstall FF. I have already switched back to using IE8 most of the time. I keep running into site unavailable, or cannot be found, or link is broken, etc, but if I past the URL into IE8, I can access the site. Sometimes I simply "try again" in FF, or I close the tab and reload the URL into a new tab. Occasionally that works, but most of the time, after I get a message that I can't get there from here, it does not work and I go to IE8. How can I get this "fixed"?? I don't run into this situation every time; it is more common when I have a large number of tabs open, say 10+. It is more prevalent when I resume a closed session, especially if it is an old session. I like the session manager approach to access previous sessions, but I will probably learn how to use IE8's Favorites approach and like it as well. What can you do for me to fix FF?? Reproducible: Sometimes Let me know if you need more info to understand the bug I'm describing. Would changing / increasing the timeout time help?? I don't sense that FF does not have enough time, but I am willing to try things...
Do you get "server not found" or another error message like timeout ? IS there a third party Firewall installed on your system ? Which router do you use ? Please try this if you get "server not found" messages : open about:config, confirm the warning, right click at an empty place and select new/Boolean , use "network.dns.disablePrefetch" as name and set it to "true" (remove the ""). That would not help in the session restore case because it's a router problem with a broken internal DNS server.
Reporter -> Are you still experiencing this issue? Have you tried the steps in comment 1?
Version: unspecified → 3.6 Branch
I must confess, I'm using a competitor's browser and I don't have that problem. I have used FF once in 4-5 months for a very short session, so I don't know if I would experience the same problem. I simply switched away from FF. Perhaps when some really new and improved version of FF comes out, I might try it again. These problems started, or at least became frequent enough when I installed 3.6. I did consider going back to a much earlier version, but when I did not run into this problem with the other browser, I never worked on it again. To have total disclosure, some of the problem might have stemmed from the router I was using at the time which was giving me a number of dropped connections. I have since replaced the router, but I have not gone back to see if the problem is still there. Thanks for your follow-up. I appreciate it. JoeD 20110205
marking incomplete without more information. Thanks for response anyway
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.