Welcome to the MacNN Forums.

Orion27 · Dec 8, 2005, 09:04 AM

I received this email from Go Daddy vis a vis the domain forwarding issue:

Q: What is the deal w/Safari Browsers and Forwarded Domains?
A: Safari made an update last week (v2.0.2) that is causing problems with forwarding domain names.
Some users have been able to get to the forwarded site by clearing the browser cache and trying again.
We found that using the Apple Network Utilities to ping the domain name will also resolve the problem.
Currently, there is not a fix available from our end.

Can someone please comment on this?

Orion27 · Dec 8, 2005, 09:09 AM

Originally Posted by Orion27

I received this email from Go Daddy vis a vis the domain forwarding issue:

Q: What is the deal w/Safari Browsers and Forwarded Domains?
A: Safari made an update last week (v2.0.2) that is causing problems with forwarding domain names.
Some users have been able to get to the forwarded site by clearing the browser cache and trying again.
We found that using the Apple Network Utilities to ping the domain name will also resolve the problem.
Currently, there is not a fix available from our end.

Can someone please comment on this?

Sorry for the double post. Safari returned a can't connect to server message so I tried again and got the the error message again. Returned to the main thread page and saw my double post.

mania · Dec 8, 2005, 07:32 PM

this is on slashdot - its godaddys fault.

Kristoff · Dec 9, 2005, 07:46 AM

No, it's not.
From reading more on the issue, and doing my own traces, it looks like a network device (content selector) is not behaving correctly.

Orion27 · Dec 9, 2005, 03:35 PM

Whatever the issue was, it now appears to be resolved. It was curious that all threads in the
Apple discussions board relating to this issue were locked over night. The issue appears resolved.
I don't know how I missed the article on Slashdot. MacFixIt also addressed the issue.

Agent69 · Dec 9, 2005, 10:46 PM

But it was a Safari only problem? No problem with Firefox, OmniWeb, or Camino?

mania · Dec 10, 2005, 08:39 AM

Originally Posted by Kristoff

No, it's not.
From reading more on the issue, and doing my own traces, it looks like a network device (content selector) is not behaving correctly.

how do you explain that it was fixed without a Safari update then? it also affected Opera. They were violating some HTTP redirect spec according to slashdotters.

Kristoff · Dec 10, 2005, 04:52 PM

Do you think that there is nothing between your browser and the web server? Did you plug your ethernet cable right into the webserver's NIC?

Randman · Dec 10, 2005, 09:49 PM

Godaddy just plain sucks.

mania · Dec 10, 2005, 10:38 PM

Originally Posted by Kristoff

Do you think that there is nothing between your browser and the web server? Did you plug your ethernet cable right into the webserver's NIC?

whaaa???

i make a request to the webserver and the webserver responds to my request. are there magic TCP gnomes changing things on the way? have you ever run a web server? do you know what redirects are? please do explain i am very curious as to what will no doubt be a highly technical explanation.

Big Mac · Dec 10, 2005, 11:08 PM

Originally Posted by Randman

Godaddy just plain sucks.

Do you say that only because of this redirect issue? Godaddy is infinitely better than Network Solutions.

Randman · Dec 11, 2005, 02:17 AM

I say it because they are the absolute bottom in every category. I loathe that company.

Kristoff · 01:29 PM

Originally Posted by mania

whaaa???

i make a request to the webserver and the webserver responds to my request. are there magic TCP gnomes changing things on the way? have you ever run a web server? do you know what redirects are? please do explain i am very curious as to what will no doubt be a highly technical explanation.

Yeah, there are these things called switches and routers that most certainly re-write packets and frames along the way.
You are looking at it from purely the application layer without regard to what might be actually happening at lower layers that would cause issues in certain circumstances.

RFCs sometimes have vague aspects to them, and can be susceptible to interpretation. If not every device in the chain is on the same page so to speak, you could have issues appear only under certain cases.

mania · Dec 11, 2005, 04:38 PM

Originally Posted by Kristoff

Yeah, there are these things called switches and routers that most certainly re-write packets and frames along the way.
You are looking at it from purely the application layer without regard to what might be actually happening at lower layers that would cause issues in certain circumstances.

RFCs sometimes have vague aspects to them, and can be susceptible to interpretation. If not every device in the chain is on the same page so to speak, you could have issues appear only under certain cases.

even so, it would still be godaddys fault would it not?