title: Abort an asp.net request without sending any response to the client
body: <p>My little ASP.NET MVC application is getting quite a few requests to bogus "setup.php" pages (easily 200+ per week). I'm guessing this is some bot attempting to find vulnerable sites on the web to hack. It's not a huge issue, but it does tend to fill up my error logs with junk and can make it harder to find real issues that need to be fixed.</p>
  
  <p>What I'd like to do is create a route to handle all .php requests (and potentially other clearly bogus extensions) and handle them in some way. What would be fantastic would be to immediately abort the request so that my application isn't wasting time/bandwidth on creating and sending a response (even if it's just a 404). Also, assuming these are malicious requests, it would be great to make their server sit and wait for a timeout instead of getting an immediate response and quickly moving on to try someone else's servers :)</p>
  
  <p>So, I guess this is a 2 part question.</p>
  
  <ol>
  <li><p>Is it possible to simply stop processing a request in ASP.NET/MVC without sending a response</p></li>
  <li><p>Is there a better solution to this issue?</p></li>
  </ol>