gshannon - 12:53 am on Feb 15, 2011 (gmt 0)
It is a somewhat different case with respect to the robots.txt ignorance.
However, appspot is subject to quotas and rate limits, in this case my best guess would be that the robots.txt request failed and the spider went on ahead anyway.
Try "inurl:forums.aws.amazon.com inurl:appspot.com" you can see some other attempts here.
The other attempt ('http://itechgiz-proxy-server.appspot.com/forums.aws.amazon.com/index.jspa') fails with a 503 over quota limit so this could be why we do not see this ranking.
I have become somewhat of an expert on debugging this as I have had three major sites that I worked on for previous clients become subject to this attack, hence why I developed the above code.