Closed Bug 177862 Opened 23 years ago Closed 20 years ago

URL could not be found

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: hans.gatu, Assigned: dougt)

References

(
URL
)

Details

Attachments

(1 file)

Alert message
7.21 KB, image/jpeg
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1) Gecko/20020826 Quite often (too often) I get an Alert that sais that the URL could not be found. Example: " www.mozilla.org could not be found. Please check the name and try again. " It can happen with any URL and mostly it works on the second try. But sometimes it takes 4 or 5 times to make it work. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. Expected Results: It should have found the URL on the first try. I use the Swedish version of Windows 98SE I use the old classic Netscape theme I use Mozilla 1.1 but the same happened in Mozilla 1.0
Attached image Alert message —
Mozilla 1.1 is really too old to report bugs against now - please consider getting a newer build and also reading the bug-reporting guidelines. Are you using a proxy?
Reporter mailed in private mail: "No I am not behind a proxy" Reporter: Does this behaviour also occur with recent builds?
I have the same problem since some days too, with different trunk-builds. After deleting the cache the page loads without problems, sometimes a force reload is enough. But it's not reproducable.
I have the same problem in Moz 1.2, Windows 2000/SP3, No proxy settings, NetGear RT314 gateway router, SurfBoard SB3100 Cable modem, Comcast cable service. Often (dozens of times daily) the DNS lookup will fail the first time, after about 5 seconds (estimated), and will work fine immediately on the second try. I have tried setting different DNS servers in Windows 2000, but the problem is still there. I even increased the Win2K DNS cache size, hoping the problem would be less (It seems to be a little less for sites I visit regularly, but I'm not really sure). I'll install Mozilla 1.3 as soon as it comes out to see if I still have the problem.
Correction to comment #5 : I am having the problem in Mozilla 1.1, and will upgrade to 1.2 as soon as it is released.
-> networking
Assignee: asa → dougt
Component: Browser-General → Networking
QA Contact: asa → benc
I have consistently gotten this problem using Netscape 7 and Mozilla 1.1. This morning I installed Mozilla 1.2.1 and recreated it trying to reach www.amazon.com. I am running Windows 2000 using direct connection to an ISDN line. I do not have pipelining turned on (this was a suggestion from a news group). About half the time clearing the cache and retrying the link will work, but I often have to use Internet Explorer to reach the link first, then retry it (so I can put the page in a tab). I would almost suspect a timeout, but the "not found" message pops up immediately. There is a lot of variation in this. Sometimes I can go a week at a time without any problems. I have never seen this with a few sites (www.google.com, msdn.microsoft.com are two I use frequently that so far have always worked).
same here, i thought it was uunets crappy nameservers ;)
I have the same problem since a couple of days. I get many 404 messages like this one : =================================== Not Found The requested URL / was not found on this server. Apache/1.3.27 Server at www.mozilla.org Port 80 =================================== I got the problem with : http://www.mozilla.org/ http://www.acers.org/ http://www.koha.org/ etc. It's always showing reference to Apache/1.3.27 server. I sometimes can reach the website if I empty the cache, close Mozilla and open it again. Or if I previously reached the website with Konqueror and then Mozilla sometimes manages to get through... I'm using Mozilla 1.3 on Mandrake Linux 9.1. I don't have pipelining enabled. I don't remember having touched my Mozilla parameters lately.
Follow-up to #5 It could be a coincidence, but I seem to get far fewer temporary "Page Not Found" errors after replacing my Netgear RT314 router with a $29 Seimens SpeedStream 2604 router. Also, DHCP works much better from the new router. I'm now running Mozilla 1.3
*** Bug 214292 has been marked as a duplicate of this bug. ***
*** Bug 216135 has been marked as a duplicate of this bug. ***
*** Bug 221412 has been marked as a duplicate of this bug. ***
I don't think I've had this problem in a while. I'm using Mozilla 1.5 now (Win2K/SP4). It might have gone away when I change my ZoneAlarm settings. Is anyone still having this problem?
We had a recent check-in to fix a DNS regression. Does this problem still occur with Mozilla 1.7 RC1 or later?
I have been plagued by this problem in Mozilla 1.6 with Windows XP Professional SP1a, but I have been reluctant to install Mozilla 1.7 until the final is released. I never encountered this problem in Mozilla 1.5. It seems to have been introduced in 1.6.
I too have been plagued by this problem. I have had it since I was using Netscape 6, also have had it with NS 7, NS7.1, up to Moz 1.7.8 and Firefox 1.0.4. I have had it on Win98 and WinXP, 56K Dial-up and ADSL, from behind a proxy and with direct connection on several different pc's and the people that I have turned on to Firefox or Mozilla have also told me that they have had the same problem. Some of them got so irratated by it they went back to IE. It seems to be worse on slow connections but it also occurs on faster connections. A site that is valid (have gotten it several with www.mozilla.org, but also other sites) gives the popup message the first time and if you try again immediately it goes through. On slower conections especially if I am downloading files at the same time I usually have to try several times before it goes through. The problem occurs erracticly. I ahve tried increases the values in about: config for network.http.connect.timeout and network.http.request.timout but it did not help.
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
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: