Page not viewable in Safari

So the recent update, as has been pointed out, is not
the issue. Whether GoDaddy exposed a flaw in Safari,
or just did something that isn't a good idea,
code-wise,I can't say. Not enough of a web guy to
know that. But I can't figure out why it's so hard
for GoDaddy to just drop a line to Apple and discuss
this on behalf of their customers. I mean, even IF
Apple were to blame, GoDaddy still should have an
interest in getting to the bottom of this.

The Safari market in miniscule compared to other browsers. The squeaky-wheel tactic must be applied. Keep those cards and letters coming kids!

Yeah I hear ya, but it's not like Apple is some under-the-radar company. A customer is a customer. But I am sure your comment is true regarding GoDaddy's attitude.

Been a Mac user for over 10 years, so I am used to playing second fiddle. But this situation isn't something for which GoDaddy has to restructure their entire company – just tweak some code so it plays nice with Safari.

I'll be dropping GoD a line shortly.

Colin...THANKS! i'm not that techy when it comes to internet stuff but all that sounds good to me. did you send it to godaddy???

THANKS AGAIN!
j

Yeah I hear ya, but it's not like Apple is some
under-the-radar company. A customer is a customer.
But I am sure your comment is true regarding
GoDaddy's attitude.

Been a Mac user for over 10 years, so I am used to
playing second fiddle. But this situation isn't
something for which GoDaddy has to restructure their
entire company – just tweak some code so it plays
nice with Safari.

I'll be dropping GoD a line shortly.

i'll be dropping the period if somethings not done SOOOOON!
xo
j

GoDaddy seems to be coming around. Here is my email to them and their respnse:

QUESTION
Hi,

What are you doing to address the known issue with forwarded domains
appearing blank in Safari? This issue is getting a great deal of press,
and most of it is not very flattering of your company. Your tech reps
seems to be making things up when people call about this issue. The
problem is well documented and it is clear that it is only an issue with
your service. Unless you can give me a straight answer about what you
are doing to correct this problem, I will have no choice but to move my
23 domains to someone else. There is already a great deal of talk on
messages boards from people who have already started moving. You need
to deal with this soon, or you will regret it.

Thank you for your time,

Vince
VC Web Design
http://www.vcwebdesign.com

RESPONSE
Dear Vince,

Thank you for your email. GoDaddy learned that some customers using the Apple Safari web browser were having difficulty accessing forwarded domain names. At this time, we have determined the issue is NOT related to a glitch in our service, but rather with a product supplied by one of our vendors. We are actively working on resolving this issue and expect it to be fixed shortly.

Please let us know if we can help you in any other way.

It is by far the most descent reply we have seen here. At least they aknowledge there is a problem. Though even if they fix it, now my trust to them is not as high as before. After two weeks with all the info been given to them, now they come up with this. Anyhow, we have to wait and see. Still I'm considering moving out though.

Demos

Well at least they are taking responsibility for the problem and not trying to blindly and foolishly pass the buck on to Apple. I wonder now how long it will take to fix their problem. I have also heard enough BS from them to where I would not be surprised if the problem is not fixed soon, and someone contacts them again, that we won't get the ol' "It's Apples problem" again.

I guess we wait and see, again.

I will probably be jumping ship anyway, but it would be nice for my sites to be up again until I can do some research about where to go.

I just got the same reply (and was about to post it). At least there is a consistent answer from GoDaddy support now, which hopefully means they are taking notice.

I read their response again and am happy that they are admitting there is a problem and are working to fix it, but after them passing the buck to Apple all this time, the following statement made in their reply P's me off:

"...we have determined the issue is NOT related to a glitch in our service, but rather with a product supplied by one of our vendors."

First of all, I don't care where the problem is coming from, it is on their end and IS RELATED TO THEIR SERVICE! He could have said something like, "we have determined that it is not a glitch in our codeing or the way we have it setup, but it is a problem with a vendor that we use with our SERVICE.".

Their service is to provide domain registration and forwarding and masking of those domains. If any of that does not work and it is because of something that they have done or did, then it IS a problem with their SERVICE.

I am done with my rant, but they have got me worked up over all the finger pointing and BS they tried to push onto us all.

Last night I thought I would experiment a bit. I removed my domain masking from my forwarded domain. I gave it about 8 hours and tried the address. it worked, while one of my other forwarded domains with masking was not working. so after trying it again this morning with the same results I decided to turn the masking back on and see what happened. again, I gave it about 8 hours to take affect. I just tried it and it worked, with masking, while the othe domain, which I never switched the masking off and on is still not working. very weird. here are the urls:

http://www.adamshiver.com
http://www.insipidthoughts.com

the first one is the one I have turned the masking off and back on. the second is the one which I have not modified since all of this began. I have no clue what is different here. but it's very weird to me.

HTTP/1.1 302 (Found) Moved Temporarily
Location: /?ABCDEFGH
Content-Length: 0
Client-Date: Thu, 08 Dec 2005 17:08:51 GMT
Client-Peer: 64.202.167.129:80
Client-Response-Num: 1
Client-Warning: Redirect loop detected (max_redirect
= 0)

Note the last line, about redirect loop detected.

I think you're onto something there. I did some various testing, and I think what's going on is something screwy with the way their redirect service works.

In my testing, regardless of what user agent I use or what client I use, I invariably get the redirect loop for 1 or sometimes 2 iterations before it finally responds with the 302 Found message and points me to the right place. Subsequent requests invariably go straight to the 302 Found response. Until I let some time pass, and then I get the 302 Moved Temporarily loop again.

What I think is happening is that their redirection system is coded to be a "real-time" setup. That is, it's guaranteed to provide you an answer in some kind of reasonable time. When it goes to look up the information in it's redirection database, if that takes longer than expected, you get the loop response back, which makes your browser submit the request again. Once you do get the Found response, that information is cached somewhere, and so subsequent hits to it are fast enough to not shunt you into the loop. Until their cache expires, of course.

And it sounds like Safari doesn't much care for redirect loops.

This explains all the observed behavior.
-Why it works in some browsers but not others (some don't like loops as much as others)
-Why those browsers work after you actually get it to work (that cache on their end)
-Why this happens even if you use browsers on different computers through a router (the cache might be keyed to requesting IP address)

In the end, it's still GoDaddy's problem, but it is unusual that Safari (and Opera) won't follow redirect loops.

Well, here's a new response from Go Daddy. Seems a little defensive, although I hope it means they're working on the problem:

Dear xxx,

Thank you for contacting customer support.

Safari is not a browser which we develop which means that we cannot simply change the way it operates. We are currently working with the necessary companies to assist in correcting this issue.

Please let us know if we can help you in any other way.

I read their response again and am happy that they
are admitting there is a problem and are working to
fix it, but after them passing the buck to Apple all
this time, the following statement made in their
reply P's me off:

"...we have determined the issue is NOT related to a
glitch in our service, but rather with a product
supplied by one of our vendors."

First of all, I don't care where the problem is
coming from, it is on their end and IS RELATED TO
THEIR SERVICE! He could have said something like,
"we have determined that it is not a glitch in our
codeing or the way we have it setup, but it is a
problem with a vendor that we use with our
SERVICE.".

Their service is to provide domain registration and
forwarding and masking of those domains. If any of
that does not work and it is because of something
that they have done or did, then it IS a problem with
their SERVICE.

I am done with my rant, but they have got me worked
up over all the finger pointing and BS they tried to
push onto us all.

i hear you jester! AGREED!
it's like they're afraid to say we made a mistake. how annoying!
shifting blame once again. i guess they feel they can't admit to the blame because they kept saying..."it's not our fault".
i wish they would just say "it was a problem on our end. we apologize and we are dealing with it as swiftly as possible. " this company needs some morals and a BACKBONE!

Well, here's a new response from Go Daddy. Seems a
little defensive, although I hope it means they're
working on the problem:

Dear xxx,

Thank you for contacting customer support.

Safari is not a browser which we develop which means
that we cannot simply change the way it operates. We
are currently working with the necessary companies to
assist in correcting this issue.

Please let us know if we can help you in any other
way.

i didn't realize they developed any browsers!!! lol