cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

Wrong HTTP header HTTP/1.1 302 Found should be HTTP/1.1 200 OK on server at IP 50.62.113.1

I am getting errors all over the place since the headers are wrong on server IP 50.62.113.1. Initial headers are HTTP header HTTP/1.1 302 and should be HTTP/1.1 200 OK. If you refresh the headers twice you start to get HTTP/1.1 200 OK. Either Mod Security is doing something wrong or the 4gh server needs to be looked at at IP 50.62.113.1. All URLs are doing this on that server.

 

Google Webmaster Tools:

We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit.

Redirect error: Redirect error HTTP Error: 302

 

Facebook Debugger:

Could Not Follow Redirect URL requested a HTTP redirect, but it could not be followed.

Circular Redirect Path Circular redirect path detected (see 'Redirect Path' section for details).

Response Code 302 Server IP 50.62.113.1

 

Any website located on the server at 50.62.113.1 initially gets the wrong header. Check any URL on that server at http://www.webconfs.com/http-header-check.php

HTTP/1.1 302 Found =>

Connection => close

Pragma => no-cache

cache-control => no-cache

Location =>

2 REPLIES 2

Re: Wrong HTTP header HTTP/1.1 302 Found should be HTTP/1.1 200 OK on server at IP 50.62.113.1

Here is a list of sites on that IP, test anyone of them and see what the header is

http://hipster-coder.com/ip/50.62.113.1

 

Any type of file even a txt and static html will give you the same issue

 

Also note that the node acc131da is using about 3x the CPU than the other 3 nodes on that server cluster.

 

New

Googlebot Receiving HTTP/1.1 500 Internal Server Error

Can someone please help me figure this out. I've called - changed things, added SSL certificates and googlebot still continues to receive a - I've been trying to submit the robots.txt and sitemap - they are simple and plain and in Google Web Tools it kicks back a 500 error. See response below.

HTTP/1.1 500 Internal Server Errorgoogleboterror500.png