lucy24 - 11:22 pm on May 22, 2012 (gmt 0)
From the topic header:
why did it get a 200
Was it supposed to get a 403? I've had similar headscratchers, and they tend to come down to UA rewrites. For example, if a nasty robot pretends to be MSIE 5, it will get rewritten to a special page. So it may never meet the later rules that would have kicked in if a normal UA had made the same request.
There are other possible explanations, but they all come down to: Even though logs say 200, your visiting nasty didn't actually get what it wanted.