GoDaddy Customers: Very Important Info

If your request is

GET / HTTP/1.0<CRLF>
<CRLF>

, then you will get the default page for the current server, which is usually something saying "go away". The status code will be 200.

If the request is

GET / HTTP/1.0<CRLF>
Host: www.psychlinks.net<CRLF>
<CRLF>

, then you will get a 302 response pointing to www.psychlinks.ca.

J.D.

 

Speaking of http codes, this is hilarious:

http://www.thinkgeek.com/tshirts/ladies/6792/

Summer?

 

Hey, those are valid codes! Too bad it'd be hard to find someone who'd appreciate these

 

Thanks this tool is useful.

 

I just transfered all of my forwarding accounts to sedo parking because of this... I used another tool that displayed a 200 on all the forwarding accounts I had and now when I used the tool in this thread I got 302's....

Hope nothing gets effected because I had alot of them, but all looks ok right now....

 

I'm not trying to say the 302 redirect is unfriendly, merely reflecting in my answer the current issue of the 302 PageRank stealing exploit with Google that has been discussed in many webmaster forums.

The example provided by Ajeet at the beginning of this thread is the perfect example of what makes the problem so difficult to deal with as far as Google is concerned: that of inadvertant redirects and webmasters who don't have the necessary skill sets to know any better, or who have restricted access on what they can and cannot do on the server which hosts their domain.

Many managed hosting sites do not allow sufficient control by the webmaster to adequately deal with redirects. Hell, some don't even let you customise a 404 Error page, never mind get specific with redirected pages and returned responses.

 

This shouldn't have to be about the skill set of the webmaster in question though.

This is a Google flaw. Scratch that, a google F**k up, that still hasn't been fixed.

 

Same here: I still see a 200 OK returned from my parked/forwarded site:

 

See my post #21 for an explanation on why you see 200 in your case.

J.D.

 

I did see that, JD...

My point is that the referenced tool is where I see the "200 OK". And it looks like clasione was seeing something similar. So how useful is the header tool? I also tried a few other similar tools on the net and I got the same thing...

 

I have seen recently godaddy use the 302 to get high PR on an old domain name that I thought about buying for the possibility of old customer of related products, but then google reregistered it themselves. Godaddy knows the game they play.

 

I see. Well, it seems that this tool doesn't send the Host header, which throws off the web server (this header determines which virtual website will serve the request). Not much use in a tool like this (this header is mandatory and some servers will reject a request that doesn't have one, even if the website is bound to a static IP address).

J.D.

 

is solved this problem at the end ?

 

Cheers! was just looking for a header checker tool, now lets hope it works lol