title: Best practice for handling wrong HTTP verbs
body: <p>We have the recurring issue with either users reloading pages or attacks sending:</p>
  <ul>
  <li>POST to GET actions</li>
  <li>GET to POST actions.</li>
  </ul>
  <p>Especially the hacking part floods our logs with errors while trying all kind of url parameters...</p>
  <p>Obviously this results in a</p>
  <blockquote>
  <p>HttpException: A public action method 'xyz' was not found on controller 'abc'</p>
  </blockquote>
  <ul>
  <li>Should we add the <em>other</em> action as well and return 404 Not Found or 400 Bad Request?</li>
  <li>This isn't entirely an asp.net issue. How do other frameworks handle this?</li>
  </ul>
  <p>We could also just filter the error messages but this seems kind of a cover up...</p>