Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Sat Sep 06, 2008 5:29 pm 
Offline
Newbie

Joined: Sat Sep 06, 2008 5:25 pm
Posts: 2
60.172.219.6 - - [05/Sep/2008:08:49:53 -0400] "GET http://thecric.free.fr/AZenv/azenv.php HTTP/1.1" 301 178 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)"
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; +http://www.google.com/bot.html)"
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; +http://www.google.com/bot.html)"
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; +http://www.google.com/bot.html)"

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 http://thecric.free.fr/AZenv/azenv.php

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.


Top
   
 Post subject:
PostPosted: Sat Sep 06, 2008 5:35 pm 
Offline
Junior Member

Joined: Fri Jun 27, 2008 12:24 am
Posts: 31
Google will commonly look for pages that shouldn't exist so it can detect your 404 handling. This is documented somewhere in Google's spider docs. It's nothing to worry about.


Top
   
 Post subject:
PostPosted: Sat Sep 06, 2008 6:18 pm 
Offline
Senior Member
User avatar

Joined: Tue Apr 13, 2004 6:54 pm
Posts: 833
The first entry is someone in China (based on IP address) looking for open web proxies. You're giving an error, so that's fine.

Now I'm not sure why you're returning 301 errors for stuff, but it's not a big issue.

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)


Top
   
 Post subject:
PostPosted: Sat Sep 06, 2008 8:48 pm 
Offline
Newbie

Joined: Sat Sep 06, 2008 5:25 pm
Posts: 2
Ahh... I'll have to look at the 301 errors. Thanks for the info.

I'm playing with nginx and I haven't quite got the error handling figured out.


Top
   
 Post subject:
PostPosted: Sat Oct 18, 2008 9:33 am 
Offline
Senior Member

Joined: Fri Feb 13, 2004 11:30 am
Posts: 140
Location: England, UK
301 isn't an error. It means "Redirected Permanently". My guess is that it's sending a redirect to the original URL itself.


Top
   
 Post subject:
PostPosted: Sat Oct 18, 2008 9:56 am 
Offline
Senior Newbie

Joined: Sat Oct 11, 2008 11:49 am
Posts: 12
Ciaran wrote:
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.

_________________
http://zombie-slaughter.co.uk


Top
   
 Post subject:
PostPosted: Sat Oct 18, 2008 10:45 am 
Offline
Senior Member
User avatar

Joined: Mon Jul 21, 2008 1:26 pm
Posts: 171
Website: http://www.rejecttheherd.net
Location: Seattle
DataMatrix wrote:
Ciaran wrote:
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.



RFC 2616

Quote:
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.

_________________
Image
Where "Thought Crime" is commited
http://www.rejecttheherd.net


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group