Don't be tricked into thinking the problem is fixed. Remember, if you use Firefox first, then one of the browsers that didn't work before, everythin appears to work fine.
I think the GoDaddy servers cache the forwarding URL for some short period of time, thus giving the impression the problem is fixed _after_ you use Firefox or MSIE. If you query GoDaddy with Firefox, then query it again with firefox, it returns a proper 302 header with full URL, so their server responds differently once it has a sucessful connection. This is one of the things that screwed up my analysis of the problem, because it seemed "intermittent" as I played with different browsers. After using Firefox, Lynx would work for a while, then it would fail again.
This is bullshit. Try using the command line lynx or curl browsers... it fails with them and they are not dependent on Java. This is a configuration error on GoDaddy's servers that started around November 28. Before then Lynx, Curl, Safari, and Opera all worked find when interacting with their forwarding service.
The problem is GoDaddy doesn't know what the #&#&^ they are doing. BTW, this not only affects Safari and Opera, it affects every since CLI browser I know...
I tried resolving this with GoDaddy when this started around Nov 28 (the weekend of Thanksgiving). I talked to tech support and sent the captured network traffic showing them the URL from the 302 header was pointing to the wrong "/?ABCDEFGH" relative URL. I clearly said that they should forward this to the people in charge of the servers.
1) Response number one: Check your firewall settings. We don't see this so it must be your fault.
2) I email them, explaining this is happening from computers I have access to in Virginia and Minnesota and four different ISPs. This is not a configuration error on my computer. I again send them the network packets I captured. The response, please check your firewall settings and it can't be their problem because no one else is seeing the problem.
3) I end up investigating starting with a Google search for "/?ABCDEFGH" and find out that Apple's Webkit developers have been seeing the problem. They seem to consider it to be a glitch in Safari that it doesn't handle the malformed 302 header from GoDaddy (the same way that certain old tags keep getting supported even if they are depreciated). Firefox and MSIE work because they handle a malformed 302 header with a relative URL link (which is, I believe, not supposed to be used). My impression was the people on them mailing were trying to patch WebKit. I forwarded the following email to GoDaddy tech support,
From my investigation of the problem locally, it seems to be that the problem is with browsers that don't handle the "302 Moved Temporarily" header returned by your domain forwarding web server properly. It appears that most command line clients also don't handle "302 Moved Temporarily" properly.This seems to be what is expected to happen:
User requests / from your server because they were directed there by a DNS identification of http://family.cabanela.com/ pointing to your server.
GoDaddy Server redirects to/?ABCDEFGH ("302 Moved Temporarily")
User requests/?ABCDEFGH
GoDaddy Server prepares new version of/, and redirects user back to /
The reason this doesn't work in my command line browsers is that they give up at step 2. When they get the "302 Moved Temporarily" HTTP response, they don't load the URL to which the server reports the page has moved.The reason this works in Firefox is that Firefox continues to step 3, loading the URL to which the server reports the page has moved.The reason this works in my command line browsers after you try it in Firefox is that Firefox has already gone through steps 1-4, so your server apparently already has the "real" / ready to go. So this appears to be an issue due to the fact that you must cache the URLs to be forwarded on your server and once in the cache, they play friendly with any browser (on any client, I suspect).
[snip]
The reply from GoDaddy's tech support:
Thank you for contacting customer support. We are aware of the issue being experienced with forwarding. There is a problem with the connection between several ISP's and our servers. Unfortunately, as the problem is not with our servers, we are not able to fix it ourselves, nor do we have an ETA for when the problem will be resolved. Your sites are currently forwarding correctly. You should be able to verify this with and . Your ISP may be able to give you more information.
It's of course never their fault. I am dropping GoDaddy. If their tech support is this awful when handed the bloody details, I hate to think how they deal with people without a clue.
I made a heck of a typo when I submitted this story, 2005 EL61 is a about roughly eight times fainter than Pluto, not brighter.
The latest information is that this object is more likely to be in the ballpark of Pluto's size and not bigger. This object also does not appear to be the same 17th magnitude outer solar system object observed by the Gemini telescope earlier this year that was going to be "announced" in September at the DPS meeting. So it looks like a few of these guys may be out there.
Furthermore, it looks like it was all a misunderstanding. Just posted on the IP mailing list:
>Date: Fri, 25 Jul 2003 14:52:22 -0400 >From: Shawn Yeager >Subject: Re: pho: Fwd: Apple's Music Store policy -- the fine print for > expatriates >To: pho@onehouse.com >Cc: declan@well.com, dave@farber.net > > >Thanks to William in the Apple Music Store group (who I believe is on the >Pho list), it appears that I received bad information from their customer >support organization, and he's working on restoring my ability to play the >purchased songs. > >Thanks, William. > >Shawn
Just because idiots cite Fred Hoyle (I will note Fred Hoyle was very opposed to Creationism too, at least in the Biblical sense) doesn't make Fred Hoyle the problem.
Also, as a scientist, it can sometimes be hard, except in detailed writing, to seperate my speculations from detailed theory...there is a spectrum of thought between the two.
At the time Hoyle coined "Big Bang" as a derogatory term for that theory, the BB theory was, frankly, pretty far out there. It had General Relativity backing it, which was pretty good, but observationally it was not as strongly supported as today.
You have to remember that what makes a speculation into a well established theory is how well it makes predictions. The BB theory makes detailed predictions as to what will be seen, and so far, it has stood the test of time.
Just because some jokers take Hoyle's quotes out of context (by assuming something he said 30 years ago was his viewpoint today) doesn't make Hoyle a bad scientist.
After all, I hate to think that I will be held accountable for all my theories I espouse today 30 years from now.
Actually, Fred Hoyle coined the term "Big Bang" as a way of deriding the theory of the universe beginning at a set point in the past.
Fred Hoyle was always a proponent of the Steady State theory, which at least until the late 1980s was a reasonable (if unfavored) contender to the Big Bang. However, with the precise measurements of the fluctuations in the Cosmic Microwave Background (performed by the COBE satellite) and the subsequent measurement of the curvature of the universe with Supernovas at extreme redshifts...well, lets just say the Big Bang is a pretty good theory at predicting what we will see. Although there are still surprises out there (the universe appears to be accelerating instead of decelerating for one thing).
Funny thing is I remember a few years ago Carl Sagan and others at Sky & Telescope ran a contest to come up with a new phase for the "Big Bang" theory, because it was really a bad term (it makes people think of an explosion, which it was not), after several hundred entries, the empaneled committee couldn't decide on a better term than "Big Bang".:)
Don't be tricked into thinking the problem is fixed. Remember, if you use Firefox first, then one of the browsers that didn't work before, everythin appears to work fine.
I think the GoDaddy servers cache the forwarding URL for some short period of time, thus giving the impression the problem is fixed _after_ you use Firefox or MSIE. If you query GoDaddy with Firefox, then query it again with firefox, it returns a proper 302 header with full URL, so their server responds differently once it has a sucessful connection. This is one of the things that screwed up my analysis of the problem, because it seemed "intermittent" as I played with different browsers. After using Firefox, Lynx would work for a while, then it would fail again.
This is bullshit. Try using the command line lynx or curl browsers... it fails with them and they are not dependent on Java. This is a configuration error on GoDaddy's servers that started around November 28. Before then Lynx, Curl, Safari, and Opera all worked find when interacting with their forwarding service.
I made a heck of a typo when I submitted this story, 2005 EL61 is a about roughly eight times fainter than Pluto, not brighter. The latest information is that this object is more likely to be in the ballpark of Pluto's size and not bigger. This object also does not appear to be the same 17th magnitude outer solar system object observed by the Gemini telescope earlier this year that was going to be "announced" in September at the DPS meeting. So it looks like a few of these guys may be out there.
Furthermore, it looks like it was all a misunderstanding. Just posted on the IP mailing list:
>Date: Fri, 25 Jul 2003 14:52:22 -0400
>From: Shawn Yeager
>Subject: Re: pho: Fwd: Apple's Music Store policy -- the fine print for
> expatriates
>To: pho@onehouse.com
>Cc: declan@well.com, dave@farber.net
>
>
>Thanks to William in the Apple Music Store group (who I believe is on the
>Pho list), it appears that I received bad information from their customer
>support organization, and he's working on restoring my ability to play the
>purchased songs.
>
>Thanks, William.
>
>Shawn
Just because idiots cite Fred Hoyle (I will note Fred Hoyle was very opposed to Creationism too, at least in the Biblical sense) doesn't make Fred Hoyle the problem.
Also, as a scientist, it can sometimes be hard, except in detailed writing, to seperate my speculations from detailed theory...there is a spectrum of thought between the two.
At the time Hoyle coined "Big Bang" as a derogatory term for that theory, the BB theory was, frankly, pretty far out there. It had General Relativity backing it, which was pretty good, but observationally it was not as strongly supported as today.
You have to remember that what makes a speculation into a well established theory is how well it makes predictions. The BB theory makes detailed predictions as to what will be seen, and so far, it has stood the test of time.
Just because some jokers take Hoyle's quotes out of context (by assuming something he said 30 years ago was his viewpoint today) doesn't make Hoyle a bad scientist.
After all, I hate to think that I will be held accountable for all my theories I espouse today 30 years from now.
Actually, Fred Hoyle coined the term "Big Bang" as a way of deriding the theory of the universe beginning at a set point in the past.
:)
Fred Hoyle was always a proponent of the Steady State theory, which at least until the late 1980s was a reasonable (if unfavored) contender to the Big Bang. However, with the precise measurements of the fluctuations in the Cosmic Microwave Background (performed by the COBE satellite) and the subsequent measurement of the curvature of the universe with Supernovas at extreme redshifts...well, lets just say the Big Bang is a pretty good theory at predicting what we will see. Although there are still surprises out there (the universe appears to be accelerating instead of decelerating for one thing).
Funny thing is I remember a few years ago Carl Sagan and others at Sky & Telescope ran a contest to come up with a new phase for the "Big Bang" theory, because it was really a bad term (it makes people think of an explosion, which it was not), after several hundred entries, the empaneled committee couldn't decide on a better term than "Big Bang".