Safari hassle. ..

[beacher]

2 hard drives, 1 w/10.4.11 & the other with 10.5.8 and both of them often give me this message when I try to go to my homepage:

"Safari can’t open the page.
Safari can’t open the page “http://cm.my.yahoo.com/”. The error is: “bad server response” (NSURLErrorDomain:-1011) Please choose Safari > Report Bugs to Apple, note the error number, and describe what you did before you saw this message."

I hit the reload button, and the page comes up! I've tried deleting the plist, to no avail. . . Any suggestions?

Also, in mail, in the preferences, I have the "Composing: Message Format:" as Rich Text, and yet, about half the time, when I go to italicize a text, the box pops up and asks me if I want to convert to rich text.  What's up with that?  And, it also happens on both platforms!

As usual, thanks in advance!

[Xairbusdriver]

1. First, make sure you are using the latest version of Safari. Then, report the problem to Apple. They actually keep, compile and work these reports. And it's a free service.

2. Try setting Rich Text as your preferred choice in Mail prefs (Composing). You might also see if you have checked the "Use the same message format as the original..." in the Responding section of that pref tab.

If this doesn't stop the inconsistent behavior, stop using the menu item and just answer 'OK' at the first prompt. Also, remember that many of us won't even see the RTF. We like plain text for several reasons.

[krissel]

Hi Ed, two things you can do.

First, dump the Safari cache and restart the app.

Second, you can try eliminating the "cm" in the yahoo address which will take you to a different server within the Yahoo network.

http://my.yahoo.com/

Info on the network:
http://www.robtex.com/dns/my.yahoo.com.html
http://www.robtex.com/dns/cm.my.yahoo.com.html

[Xairbusdriver]

That Yahoo address works for me in Safari 4.0.4. But it may have more to do with what Kriss suggested about clearing your Safari cache. Unless you have a rather slow connection, I'd suggest keeping a rather low setting on your Safari cache. That can help force Safari (or any browser) to make another attempt to access the page instead of using the 'bad' info in the cache. That may simply be a slow response from the sites's server, which could work the next time it is actually accessed. You might also want to enable the Debug menu by using Cocktail. And the Develop menu in the Advanced prefs tab. Both of those menus have ways of clearing/disabling the multiple caches or seeing other pertinent info about them.

[beacher]

Thank you both for the suggestions; I'm pretty sure that Kris nailed it with the "cm." thing, as I emptied the cache, and eliminated that from my home page address, and have not had it reoccur at all today!  Happy camper, once again!