Slashdot Mirror
GoDaddy Serves Blank Pages to Safari & Opera
zackmac writes "For over two weeks domain registrar GoDaddy has been serving blank pages to Safari and Opera users who attempt to access sites using its domain forwarding and masking service. GoDaddy is blaming Apple as the source of the problem, and with nowhere to turn, Mac users are flocking to Apple's support forums to discuss the issue in-depth. Apple has so far been unresponsive and GoDaddy has directed affected customers to contact Apple Support. An inconvienent workaround is to open the website first in Firefox or Internet Explorer and then the page will load in Safari or Opera. Speculation abounds as to the cause of the problem and how to fix it. The current belief is malformed headers, an invalid 302 header with a bogus location and a redirect loop."
GoDaddy blames Apple for both Safari and Opera simultaneously ceasing to work? That's a nice trick
The best solution to this problem is to avoid Godaddy entirely. They are fast making Verisign and ICANN look reputable.
Yeah, and those Location: headers are broken as well. Although most browsers accept them and act as implied, they really should specify fully-formed URLs -- i.e. beginning with http://server/ as opposed to a relative path fragment.
-b
myselfmusic
When I click on the Gallery link I get a 1" x 1" box with a lower case "f" in it. :)
Most likely, If i click the "f" a macromedia flash animation will appear. I'm not willing to take that chance.
I'm using firefox on linux and I use the firefox flash blocker extension.
The government which is strong enough to protect you from everything is strong enough to take everything from you.
Yepp. Me too. Blank on Safari.
Broken redirect usage. This provider is the suxx0rsz.
You are in the postition to ask them to change the
behaviour of their servers to RFC compliance.
I'd suggest you do it.
And change the provider if they don't fix it.
We suffer more in our imagination than in reality. - Seneca
I would agree with you except for the fact that the error is obviously on GoDaddy's end, and they are blaming Apple. If the article stated that there was a problem, and GoDaddy had no intention of fixing it because it only affect a small number of people, it would be unfortunate, but expected. As it is, they are trying to pass the buck and blame someone else. Also, point of fact, Safari and Opera have more than 0.25% marketshare. So, all things considered, your post is a troll. Rather than mod you down, I thought I should explain why you will be modded down by someone else shortly.
Rhapsody in Numbers
Comment removed based on user account deletion
Less of the elitism please. While it's very simple to confirm that they are sending malformed headers, that's not to say that the headers are the origin of the problem. In case you haven't noticed, the web is full of broken code, just because you see something that doesn't adhere to the RFC, it doesn't mean that this is necessarily what is causing the problem.
Bogtha Bogtha Bogtha
Disclaimer: I do not work for Godaddy, in fact I work for a competing ISP and domain registrar that is also in GoDaddy's local area:
That being said, I must say that everything I have ever learned by talking to existing Godaddy customers, Godaddy employees whom I know, and observation in general, I can say that what I have noticed conflicts with what you have said entirely. I realize that there is always bound to be someone who is going to be unhappy (e.g., you can't satisfy all the people all of the time) but honestly your complaint is the first I've ever heard of with Godaddy -- which is pretty amazing considering how many customers they have.
Another thing I like about them in particular, in addition to (again, what I believe, personally) their good reputation as a web hosting services and domain registrar is that they do not tolerate spammers and make a fairly decent effort to terminate them as they discover them (e.g., source: news.admin.net-abuse.email
My $0.02.
It's true no man is an island, but if you take a bunch of dead guys and tie 'em together, they make a good raft.
A full path would still resolve to the same location and contain the same bug. and the problem is about caching temporary redirects.
tl;dr: Blame Apple and Opera for not following the http spec. Blame GoDaddy.com for unnecessarily weird code.
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.
Huh? If you're using a product to supply a service, and that product is wonky and affects your service, then by definition it's a glitch in your service.
To be simpler: It's either the service you're providing, or the client. You've established that it's not the client.
While I applaud the posters' detective work, this is a test that a network admin at GoDaddy should and could do if he had half a braincell.
There ain't no rules here; we're trying to accomplish something.
The current belief is malformed headers, an invalid 302 header with a bogus location and a redirect loop.
That's not it. That's not it by a mile. The real cause of this problem is that GoDaddy never bothered testing their site with anything other than two browsers. Hell, they probably only tested it with IE and the FF users just got lucky.
What the fsck is it with web developers that they never ever test their pages? And what is it with their managers that they don't insist on testing?
Don't blame me, I didn't vote for either of them!
hehe. Customers screaming, reputation going through the floor and they're sitting about waiting for someone else to fix the problem...
Deleted