title: Facebook calling my deauthorize callback url results in a 400 Bad Request
body: <p>I am trying to implement deauthorize callback for a facebook application implemented in rails.</p>
  
  <p>I configured a deauthorize callback url that points to an existing route in my application. 
  However, when I remove the app from my facebook profile's app settings page, i.e. the action that should trigger the deauthorize callback, I can only see this in my nginx access log.</p>
  
  <pre><code>66.220.158.244 - - [13/Aug/2012:09:47:12 +0200] "-" 400 0 "-" "-"
  </code></pre>
  
  <p>In the rails log it does not even show. Since the ip address is in facebook's ip range it seems that facebook hits my server, but something odd is going on.</p>
  
  <p>I can successfully call the deauthorize callback url manually and when I do it shows up in the logs as expected. </p>
  
  <p>Any hints to what is happening here?</p>