实时API自签名证书 [英] Realtime API self signed certificate

问题描述

我在使用foursquare实时API和自签名证书时遇到问题.每次进行测试推送时，我都会返回您的服务器已退回:502错误的网关"，但我90％的确确定它实际上没有到达我的服务器(我已将其设置为在任何地址观看get& post，并且没有任何结果，如果我获取/发布到服务器上的任何地址，则它可以工作(本地和远程).)自签名证书和推送API是否存在某种问题?

I'm having a problem using the foursquare realtime API and a self signed certificate. Every time I make a test push I get back "Your Server returned: 502 Bad Gateway" but I'm 90% sure it's not actually reaching my server (I have it set to watch get & post at any address and nothing comes through, if I get/post to any address on the server it works. Local and remote.) Is there some kind of issue with self signed certs and the push api?

推荐答案

出现502错误，听起来像是您这一边的配置错误，与您的实际代码无关，或foursquare.一般来说，对于我们的Push API，运行自签名证书应该可以，所以我怀疑那是您的问题.

The 502 error makes it sound like it could be a configuration error on your side, unrelated to your actual code, or foursquare. Generally speaking, running self-signed certs should be fine for our Push API's, so I doubt that's your issue.

如果您还不熟悉502错误，则可以在此处进行一些阅读: http://www.checkupdown.com/status/E502.html

If you're not already familiar with 502 errors, you can read up on them a bit here: http://www.checkupdown.com/status/E502.html

我知道您说过它适用于常规的远程连接，但是您的主机可能不喜欢源自foursquare的请求吗?我们使用Amazon Web Services，因此原始IP来自大量IP地址，这些IP地址有时会出现在阻止列表中(例如，有人在Amazon Web Services上编写了行为异常的应用程序).

I know you said it was working for general remote connections, but it's possible there's something your host doesn't like about requests originating from foursquare? We use Amazon Web Services, so the originating IPs come from a large pool of IP addresses that sometimes end up on block lists (if say, someone wrote a misbehaving app also on Amazon Web Services).

这篇关于实时API自签名证书的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！