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

本文是小编为大家收集整理的关于实时API自签名证书的处理/解决方法,可以参考本文帮助大家快速定位并解决问题,中文翻译不准确的可切换到English标签页查看源文。

问题描述

我使用Foursquare实时API和一个自签名证书遇到了问题.每次我进行测试时,我都会恢复"返回您的服务器:502坏网关",但我90%肯定它实际上没有到达我的服务器(我设置了它可以在任何地址观看并发布任何地址,什么也不会通过,如果我在服务器上获取/发布到服务器上的任何地址.本地和遥控器.)自签名证书和推送API是否存在某种问题?

推荐答案

502错误使它听起来可能是您身边的配置错误,与您的实际代码无关或foursquare.一般来说,运行自签名的证书对我们的推动API应该很好,所以我怀疑这是您的问题.

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

我知道您说它正在用于一般的远程连接,但是您的主机可能不喜欢源自Foursquare的请求吗?我们使用Amazon Web服务,因此始发的IP来自大量的IP地址,这些IP地址有时会在块列表中最终出现(如果说,有人也在Amazon Web服务上写了一个不当行为的应用程序).

).

本文地址:https://www.itbaoku.cn/post/2090870.html

问题描述

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?

推荐答案

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.

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

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).