lucy24 - 9:21 pm on Jan 21, 2012 (gmt 0)
one ip has get //directory and got a 200, // is not correct is it?
I think there's a command that gets rid of superfluous leading slashes, because I get this sometimes too. If it's the only error in the request, it's handled as usual. But humans don't vroom, vroom through your site that fast; these double-slashes are all from 188.8.131.52. A lot of people have the 184.108.40.206/14 range blocked; it's robot territory. (AmazonAWS, I think.)
I was going to say that I don't see any errors in this slab (quick-and-dirty search for " \d+ \d+ " with leading and trailing space) although I note that all POST request get a 302. I hope that's intentional. But then this caught my eye:
220.127.116.11 - - [21/Jan/2012:06:19:39 -0700] "GET /espanol/_disponibles_marzo.php HTTP/1.1" 404 - "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/2008120122 Firefox/3.0.5"
How do you manage to get errors with no follow-up filesize? Is that your host being weird?