Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Page not viewable in Safari

Ok, I know that isn't earth shattering as a topic, but it gets weird.

First off, the page is a simple blogger page found at http://www.catalogueofships.com

Second, the page does appear in Foxfire (also, not earth shattering news, I know)

But here is the weird part. Immediately after I load it in Foxfire, it works in Safari for a limited time. Can anyone make heads or tails of that?

Also, this just started yesterday. No problems before. I did no upgrades to my computer or software this week.

Thanks.

mk

PowerBook 12 G4, Mac OS X (10.4.1)

Posted on Nov 24, 2005 9:28 AM

Reply
Question marked as Best reply

Posted on Nov 24, 2005 9:37 AM

My guess, based on the results of putting the page through the W3C Validator, that the problem is a combination of bad coding and using non-standard extensions. Safari is the least forgiving of browsers when it comes to pages with bad, incorrect, or non-standard coding. The W3C's own browser/editing tool, Amaya, also won't display the page.
304 replies

Dec 8, 2005 6:52 PM in response to Edward Rudd

Mostly I prefer to lurk rather than participate in discussions, as I frequently don't have much to add. But I was poking around in an old version of Interarchy and discovered something that may or may not help.

Since the practice of finger pointing seems to be well established on this board, please allow me to do some of my own!

Here is my Interarchy transcript:

GET / HTTP/1.0
Accept: /
Host: www.godaddy.com
User-Agent: Interarchy/5.0.1

HTTP/1.1 302 Object moved
Connection: close
Date: Fri, 09 Dec 2005 02:18:13 GMT
Server: Microsoft-IIS/6.0

I snipped the rest for brevity.

GoDaddy seems insistent to blame this problem on a vendor. And it would seem reasonable that they wouldn't write their own URL redirection code, but instead buy a package to run on their servers. GoDaddy's responsibility would be to ensure the package was configured correctly, and I presume they've done that.

If Edward is right that the HTTP specs are not being followed, then it seems obvious we could be looking at an undocumented feature (wink wink) in the Microsoft software that GoDaddy is using on their servers. If this is the case, then that means that Apple's culpability is simply that they don't have a hack for this server's 'undocumented enhancements' to what is supposed to be a standard protocol.

If anyone here familiar with this stuff could keep their ear to the ground for any imminent hotfixes, and post the info here, I'm sure it would be appreciated.


G4 DA 533DP Mac OS X (10.4.2)

Dec 8, 2005 6:54 PM in response to dan wool

There is some good information on that thread as well. There are some very web savvy people over there that are ripping GoDaddy for their trash code.

Here is someone that sheds some light on why Safari works after using IE or another browser...

"... However, what the server is doing seems to be fairly brain dead as well. Why would you redirect away and then redirect back? It appears that there is not cookie set between the two. The server must be remembering your IP address and serving you actual content on the second hit from that IP Address. That would certainly explain the "teaching issue" that causes safari to work with these sites after visiting with firefox."

Page not viewable in Safari

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.