Home » forums » Discussion » PowerPC Macs

SAFARI and msnbc.com

Submitted by elSarge on March 17, 2004 - 1:17am. PowerPC Macs

recently, when i go to msnbc.com (via bookmark or typing URL) i get the following SAFARI error:

Safari can’t open the page “http://www.msnbc.msn.com/�.
The error was: “bad server response� (NSURLErrorDomain:-1011)

clearing the cache doesn't help. several attempts have to be made to finally make it in. the same error pops up too when clicking on story links.

for your info:
Safari 1.2
osX 10.3.2
MS Trackball Explorer 1.0 mouse

anyone have any ideas?
Puzzled

» login or register to post comments | previous forum topic | next forum topic

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
crosby_sb's picture

Try updating panther to 10.3.

Submitted by crosby_sb on March 17, 2004 - 3:39am.

Try updating panther to 10.3.3? Anyway it doesn't work with me either, I would try microsoft internet exploror, or netscape, or anything else.
Crosby Cool Mac Mac OS

» Crosby

“The people who are crazy enough to think they can change the world are the ones who do.�

login or register to post comments

Indeed, I can load the front

Submitted by ek9hatch on March 17, 2004 - 3:40am.

Indeed, I can load the front page, but I get the same error as you when I try to open a story. My primary browser (Mozilla FireFox) doesn't even load the front page. I would guess it's msnbc having their own problems and it's not a compatibility issue.

» http://ek9hatch.tripod.com

login or register to post comments
tmtomh's picture

workin' fine for me here. May

Submitted by tmtomh on March 17, 2004 - 10:41pm.

workin' fine for me here. Maybe they had a problem and it's now fixed?

Matt

» 1 stories posted
login or register to post comments

It's a User Agent issue

Submitted by rivetboy on April 13, 2004 - 3:48am.

The way to get around this is to change the User Agent setting in the Debug menu in Safari. What Debug menu, you ask?

Type the following command in Terminal (while Safari is NOT running):

% defaults write com.apple.Safari IncludeDebugMenu 1

Then launch Safari, and you'll notice a new Debug menu right after the Help menu. There's alot of nifty things you can do with it, not the least of which is to change the string that Safari gives to a web server that it uses to identify itself. More often than not, a "broken" website in Safari will work with no problems if I change the User Agent to report Safari to the web server as something else, such as "Windows MSIE 6.0" or "Mozilla 1.1".

"Automatically Chosen" means "Safari", and I recommend having it set to that by default, and only changing it after you've tried accessing the page with Safari. This way, the admins will be able to see that you tried accessing it with Safari and failed, and will hopefully realise that there's a problem and subsequently fix it. Of course, if it's because the admins hate Apple, then they're not likely to fix it.

Oh, and if you want to remove the Debug menu, do the same thing as above, except type "0" instead of "1".

»
login or register to post comments

User Agent doesn't seem to be the cause

Submitted by M Tyson on April 28, 2004 - 7:50pm.

I tried this for a problem to a page internal to our site. Changing user agents did not resolve the issue.

The post
http://mailman.mit.edu/pipermail/macpartners/2004-February/000380.html

seems to indicate it may be a problem with SSL renegotiation and the person reports:
"the [servers]
that don't work seem to be running Apache + openssl 0.9.6x OR IIS,
whereas the ones that work are running Apache + openssl 0.9.7."

»
login or register to post comments

Like I said; more often than

Submitted by rivetboy on April 29, 2004 - 5:55pm.

Like I said; more often than not. That would be one of those "not" times. Eye-wink

»
login or register to post comments