Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I really wouldn't think it is a bug, it used to happen on mine, a long time ago. I just think it is miscommunication between server and computer.

and if it is a bug, it is very picky on who to infect.
 
I am so pissed....

I upgraded from 10.2.8 to 10.3.5 (clean installation). I kept getting a lot of blank pages in Safari for 10.2.8 (nothing too troublesome), so I was excited to get the newest version of Safari (Panther) as I though there would be some improvements. To my surprise I consistently get the error message described above about Safari not being able to find the server. Emptying the cache does not really work, deleting the preferences did not work. What am I suppossed to do? Also, Mail seems to be affected by this as well, some times it does not connect to the mail server. Apple really messed up on overlooking this. I do not know whether 10.3.4 had this problem as I upgraded straight to 10.3.5. However, I did not have this problem in 10.2.8. Does anybody know any word of whether Apple is fixing this issue? I really hope they do and I hope it is not a problem on my end because I wouldn't know how to fix it.
 
If you reload the URL, it will probably work.

Despite this thread, I still maintain that this isn't so much an Apple bug, but an Apple "bug" in conjunction with slow-to-respond-DNS-servers.
 
Yaay!!

I think I fixed the problem. I called my ISP (Earthlink) and they gave the DNS number which I eneterd into my network preferences. The problem seems to have disappeared, which I am very relieved about, yet confused as to why I didn't have this problem in 10.2.8. Oh well, as long as it is fixed. BTW, before I fixed the problem, the page would load if I reloaded it, it was just a big hassle. Check out this link to Apple forum, a lot of people have this problem.

Apple forum

The forum there also points out that it is a DNS issue, but why with Panther and not Jaguar?
 
I don't know your definition of bug...

... but if something that should work doesn't, that's a bug in my book. I should be able to browse the internet without knowing any details about my name-servers.

Panther obviously IS able to resolve the IP's anyway, so why in the world do I have to click a second time. It IS a bug, I really don't know what you are talking about.
 
Oh well. I guess I'm just lucky at home, at work, on the road at wifi hotspots, in airports, at hotels, and with all the users I have running Panther. Many, many, many users. All of us lucky. None of us have this bug. Lucky us. Unlucky you.

Seems to me if you switch to a faster response, non-overloaded DNS, the bug suddenly isn't..

Hopefully your unluckiness will be relucked for you with 10.3.6.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.