“收到空响应”使用 HTTPS 时
我有一个 Facebook 应用程序，它已经使用 HTTP 和 HTTPS 一段时间了。最近——我想大约一周前——HTTPS 停止工作了。现在它给出“收到空响应”。每次都发消息。
我的服务器确实有 SSL 证书并且 HTTPS 在服务器上运行。虽然它不是商业证书，但它是自签名的。
我知道 HTTPS 将在 10 月份成为一项要求...有人知道吗：
1）什么可能导致空响应错误，以及
2）根据 Facebook 的说法，可接受的 SSL 证书有哪些要求？自签名似乎不再有效......
I have a Facebook app that has been working with HTTP and HTTPS for some time. Recently - about a week ago I think - HTTPS stopped working. It now gives a 'Empty response received.' message every single time.
My server DOES have an SSL cert and HTTPS works on the server. It is not a commercial cert though, it is self-signed.
I know HTTPS is going to be a requirement in October... does anyone know:
1) What might be causing the empty response errors, and
2) What the requirements are for an acceptable SSL cert, according to Facebook? Self-signed no longer seems to cut it...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
过去几周我也注意到同样的问题。这是我所学到的，也许这会对你有所帮助。
该问题似乎是间歇性的，它发生在一天中的某些时间，而不是其他时间。有时，仅某些用户会发生这种情况。我设置了一个测试页面，只用 HTML 表示“Hello World”，没有其他内容，但我仍然收到错误。我检查了我的访问日志，Facebook 甚至没有访问我的服务器。
我正在使用画布。我已将 Canvas URL 设置为 https://。当我将其更改为 http:// 时，问题就消失了。我已将 Secure Canvas URL 设置为 https://，但仍然遇到此问题。我把它删掉了，因为它给出了错误。
另一件事 - 检查画布页面返回的 HTTP 状态代码 - 确保它是 200。有一次，我们将 http 重定向到 https，它返回了 302 状态，而 facebook 不喜欢这样并给出了此错误。
I've been noticing the same problem for the last few weeks as well. Here's what I've been able to learn, maybe this will help you.
The problem seems to be intermittent, it happens at some times of day and not others. Sometimes it happens only for some users. I had setup a test page that just says Hello World in HTML and nothing else, and I still get the error. I checked my access logs and facebook isn't hitting even hitting my server.
I am using Canvas. I had set my Canvas URL to https://. When I changed this to http://, the problem went away. I had set my Secure Canvas URL to https://, and still got this problem. I blanked this out since it was giving the error.
Another thing - check the HTTP status code that is returned by your canvas page - make sure it is 200. At one point, we were redirecting http to https which returned a 302 status and facebook didn't like that and gave this error.
自签名证书不足以呈现给最终用户。即使 Facebook“允许”，用户浏览器也会首先显示安全异常。 Godaddy 有非常便宜的 SSL 证书。
A self signed certificate is not adequate for presentation to an end user. Even if facebook "allowed" it, the users browser would show a security exception first. Godaddy has very inexpensive SSL certificates.
我的 SSL 证书已过期。我刚刚重新生成了一个新的并将其放置到位。旧证书需要一段时间才能从 Facebook 的缓存中超时，但情况已经看起来好多了。页面现在通过 HTTPS 加载，不过我暂时不会称其为“成功”。
My SSL certificate had expired. I've just regenerated a new one and put it in place. It make take a while for the old cert to time out of Facebook's cache, but things are already looking better. Pages now load over HTTPS, though I'll hold off calling it a 'success' for a bit longer.
我有同样的问题。 HTTPS 适用于 iframe 应用程序，但不适用于 FBML 应用程序。如果我使用 https 并请求 FBML 应用程序 - facebook 甚至不会向 CBURL（我的服务器）发送请求。在浏览器端它只是说“收到空响应”。但同一个 FBML 应用程序对于 HTTP 来说工作得很好。
我在我的服务器中使用 GoDaddy 证书，并且 iframe 应用程序使用相同的证书 - 它与 iframe 应用程序配合良好。
I have same problem. HTTPS works fine for iframe apps but not for FBML apps. If I use https and request for a FBML app - facebook doesn't even send a request to the CBURL (my server). On the browser end it just says "Empty response received". But the very same FBML app works fine for HTTP.
I'm using a GoDaddy certificate in my server and the same certificate is used for iframe apps - it works fine with iframe apps.