Won't Load Yahoo

This is not a bug in Safari, so the bug report will be ignored by Apple. The problem is either with Yahoo! or even your DNS servers. So let's try changing those to see if it will resolve your issue.

Quit all Internet-related applications, if any are running. Open System Preferences > Network and click on the Configure button. In the field where it says DNS servers:, enter these:

208.67.222.222
208.67.220.220

click Apply Now, then quit System Preferences. Restart Safari and test it to see if you can load the Yahoo! page.

Mulder

My feeling is that this problem is at the Yahoo end.

Last week I changed ISP to Verizon fios. Then the my.yahoo.com page stopped working. If I cleared all the cookies I could get the plain page (without a login). Then when I tried to login it will hang in the process. I don't think changing DNS servers will do the trick.

If I use verizon.my.yahoo.com it works. But there are links to my.yahoo.com in some of the yahoo pages that will not work even after sign in via verizon.my.yahoo.com. Yahoo is not worth the bother, so I'm going slow in debugging what must be a yahoo problem.

I'm also find it curious that Verizon hasn't registered the IP address I've been given.

Have you tried a different browser to see if the problem is replicated there? You should also create a new User Account and try Safari in that account as well.

Mulder

I have issues with Yahoo too - it will frequently hang or become slow. I had to stop using their email as auto-complete worked either intermittently or not at all. Names in my address book that used to auto complete on my windows machine (switched to Mac 4 months ago) would not autocomplete with Safari. Yahoo is not as Mac friendly as they claim, IMO.

I have had the same problem for over two weeks. I cannot load my "my yahoo" page. It gets the error:

Safari can’t open the page “ http://my.yahoo.com/”. The error was: “Operation could not be completed. (kCFErrorDomainCFNetwork error 302.)” (kCFErrorDomainCFNetwork:302)

I have tried everything. Firefox won't open it either. I even set up a new Yahoo account to no avail. I can access the page just fine on my PC at work. Do I have to wait for the next OS update to fix this?

This is not a Mac OS X problem; it's a Yahoo! problem. A 302 error means that a redirect is misconfigured (A redirects to B, which redirects to A); only Yahoo! can fix this, so you need to direct your complaints toward them via their Help pages, which will let you send them an email.

If it works on a PeeCee, then it's because Yahoo! is browser sniffing to look for Windoze browsers. Yahoo! has never made a real effort to support Macs or web standards. If you use the Develop menu in Safari to spoof IE 6 or 7, it may work; if not, then Yahoo! is also sniffing for the OS.

Mulder

Well, I took your suggestion and I downloaded TinkerTool and used the User Agent to try different browser types in Safari, but nothing will open the My Yahoo page. I e-mailed Yahoo two days ago, but they never replied.

Can you open this page?

http://partner.my.yahoo.com/

It's the same as my.yahoo.com but on a different specialized host.

No, that page won't open, either. The new security update out today involves DNS servers. I though for sure this was the fix, but it still doesn't work after the patch.

Well - I am pleased to announce that as of 11:30 this evening (Eastern) My Yahoo page finally opened. Was it Yahoo? Was it the Apple OS patch? Was it an act of God? I dunno, but it's nothing I did. Glory be to Steve. The world is now turning in greased grooves. I am at peace. Holla atcha boy.

Well, it's October and "my yahoo" hasn't opened for over a month. I have read that this is a Yahoo problem, but isn't it Apple's problem too? Why shouldn't Apple work with Yahoo to iron this out? Can't we all just get along? Come on now - Apple, Yahoo, play nice!

I've been having the same problem. Here's what fixed it:

Safari > Preferences > Security > click "Show Cookies" > type "yahoo" in the search bar > click "Remove All" = then Quit Safari.

My very next Sign-in worked perfectly.

There may be a better way to do it by deleting less cookies (over 45 in my case), but I am pretty good at keeping track of my passwords so for me it was NBD.