Why am I serving this domain?
66.249.71.11 - - [06/Sep/2008:16:16:22 -0400] "GET /robots.txt HTTP/1.1" 301 178 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +
66.249.71.11 - - [06/Sep/2008:16:16:23 -0400] "GET /[REDACTED –My Google Apps URL].html HTTP/1.1" 301 178 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +
66.249.71.11 - - [06/Sep/2008:16:16:24 -0400] "GET /fdfdkll.html HTTP/1.1" 301 178 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +
This just showed up in my nginx access logs… and I'm wondering what googlebot was looking for with in /fdfdkll.html and also why my server is executing a 'GET' to
I'm new to server hosting and I'm wondering if that is a sign that my server is doing things I don't want it to.
6 Replies
Now I'm not sure why you're returning 301 errors for stuff, but it's not a big issue.
I'm playing with nginx and I haven't quite got the error handling figured out.
@Ciaran:
301 isn't an error. It means "Redirected Permanently". My guess is that it's sending a redirect to the original URL itself.
301 is an error, but it doesn't necesserily imply it.
@DataMatrix:
@Ciaran:301 isn't an error. It means "Redirected Permanently". My guess is that it's sending a redirect to the original URL itself.
301 is an error, but it doesn't necesserily imply it.
> 10.3.2 301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request.