未调用 Facebook 取消授权回调 [英] Facebook deauthorization callback is not called

查看:49
本文介绍了未调用 Facebook 取消授权回调的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个 FB 应用程序,当我输入我的开发框地址作为取消授权回调 URL 时,在 FB 上删除应用程序后,该框会被此请求 ping 通:

I have an FB app, when I enter as the deauthorization callback URL my development box address, the box is pinged with this request after app removal on FB:

POST /facebook/deauthorize HTTP/1.1
Host: bashman.org
Accept: */*
Content-Length: 261
Content-Type: application/x-www-form-urlencoded
Connection: close

fb_sig_uninstall=1&fb_sig_locale=de_DE&fb_sig_in_new_facebook=1&fb_sig_time=1322732591.2685&fb_sig_added=0&fb_sig_user=1476224117&fb_sig_country=de&fb_sig_api_key=e39a74891fd234bb2575bab75e8f&fb_sig_app_id=32352348363&fb_sig=f6bbb27324aedf337e5f0059c4971

(这里的钥匙是假的)

但是!当我在取消授权回调 URL 中输入我的生产框 URL 时,永远不会发出 POST 请求.用 Tcpdump 对其进行了测试.我的生产机器上没有请求,为什么?

BUT! when I enter my production box URL in the deauthorization callback URL, the POST request is never made. Tested it with Tcpdump. No request on my production machine, why?

我用 mtr 检查了从我的生产盒到请求来自的 IP 地址的路由,一切正常,0% 数据包丢失.

I checked with mtr the route from my production box to the IP address the request came from, all is OK, 0% packet lost.

主机名端口和路径正确,测试了 1k 次,没有防火墙、IDS 或其他系统阻塞我的以太网插槽.

The hostname port and path is correct, tested it 1k times, no firewall, IDS, or other systems blocking my ethernet slot.

  1. 为什么不调用 Post 回调?(我该如何解决?)

  1. Why is the Post callback not called? (How can I fix it?)

如何调试以确定问题所在?

How I can debug this to determine what the issue is?

推荐答案

您可以尝试使用 facebook URL Debugger 并查看 facebook 的服务器是否能够访问您的回调 URL...
查看 facebook IS 能够检索的信息可能有助于您调试此问题.

You can try using the facebook URL Debugger and see if facebook's servers are able to reach your callback URL...
Viewing the information facebook IS able to retrieve might help you debug this issue.

这篇关于未调用 Facebook 取消授权回调的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆