title: Facebook Deauthorize Callback over HTTPS
body: <p>I've implemented a Deauthorize Callback for my canvas app. It would appear that Facebook is unable to ping the Deauthorize Callback over https, but it has no problem with http. I'm logging all connections and there is no record of pinging the callback from Facebook, though if I ping it myself it is logged. Further, if I have Facebook ping the callback via the URL debugging tool (https://developers.facebook.com/tools/debug) it is successful.</p>
  
  <p>Given that https does not work, I'm assuming Facebook's servers don't care for my certificate's issuer / authority. Is there a definitive list of certificate authorities that will work with Facebook's back end processes? Alternatively, is there a way to submit a new authority to Facebook for inclusion in their list of accepted certificate authorities?</p>
  
  <p>Edit: My SSL certificate was issued by "Starfield Technologies" which I believe is a simple DBA of GoDaddy. I normally avoid GoDaddy, but this SSL was cheap. Maybe I'm getting what I've paid for, as it were.</p>