称之为糟糕的时机,但在PayPal推出其新的开发人员界面之前,我在昨晚完成了这项工作。 我正在使用PHP / cURL,并从x.com复制了这段代码: https://www.x.com/developers/PayPal/documentation-tools/code-sample/216623
昨晚10点,它开始返回400个代码,空的响应体。 以下是响应标头:
HTTP/1.1 400 Bad Request Date: Fri, 08 Mar 2013 16:43:16 GMT Server: Apache X-Frame-Options: SAMEORIGIN Set-Cookie: c9MWDuvPtT9GIMyPc3jwol1VSlO=%7cC8szeIKENkwUqfOEYTjk-zp16RPNDC2MvLBQq9QALLYk8LcDM9kDEELRUPR_lxii1ujHBm%7cAo_aiVmV13ssvg_VFFqLkSkrVuIkUVx3O9nb09-nmQbg21hzsBAPIAIUIW8XFO_wn3c6T0%7c; domain=.paypal.com; path=/; Secure; HttpOnly Set-Cookie: cookie_check=yes; expires=Mon, 06-Mar-2023 16:43:16 GMT; domain=.paypal.com; path=/; Secure; HttpOnly Set-Cookie: Apache=10.72.109.11.1362760996493186; path=/; expires=Sun, 01-Mar-43 16:43:16 GMT Connection: close Transfer-Encoding: chunked Content-Type: text/plain; charset=ISO-8859-1我正在使用IPN模拟器进行测试。 永远不会得到“验证”或“无效”回复。 只有空白的反应机构。 还有其他人有这个问题吗?
Call it bad timing, but I had literally just gotten this working last night, right before PayPal rolled out its new developer interface. I'm using PHP / cURL, and literally copied this code from x.com: https://www.x.com/developers/PayPal/documentation-tools/code-sample/216623
At 10pm last night, it started returning 400 codes with an empty response body. Here are the response headers:
HTTP/1.1 400 Bad Request Date: Fri, 08 Mar 2013 16:43:16 GMT Server: Apache X-Frame-Options: SAMEORIGIN Set-Cookie: c9MWDuvPtT9GIMyPc3jwol1VSlO=%7cC8szeIKENkwUqfOEYTjk-zp16RPNDC2MvLBQq9QALLYk8LcDM9kDEELRUPR_lxii1ujHBm%7cAo_aiVmV13ssvg_VFFqLkSkrVuIkUVx3O9nb09-nmQbg21hzsBAPIAIUIW8XFO_wn3c6T0%7c; domain=.paypal.com; path=/; Secure; HttpOnly Set-Cookie: cookie_check=yes; expires=Mon, 06-Mar-2023 16:43:16 GMT; domain=.paypal.com; path=/; Secure; HttpOnly Set-Cookie: Apache=10.72.109.11.1362760996493186; path=/; expires=Sun, 01-Mar-43 16:43:16 GMT Connection: close Transfer-Encoding: chunked Content-Type: text/plain; charset=ISO-8859-1I'm using the IPN Simulator to test. Never get a "VERIFIED" or an "INVALID" response. Only a blank response body. Is anyone else having this problem?
最满意答案
目前,当我们升级开发者帐户时,每个人都在沙箱环境中遇到此错误。 我们目前正在努力解决此问题,但是一旦解决了这个问题,我肯定会通过这篇文章进行更新。
这是一个全新的环境,如果您遇到任何其他问题,请告诉我们,以便我们尽快纠正。
Currently everyone is experiencing this error in the sandbox environment when we upgraded the developer accounts. We're currently working to resolve this issue however I'll be sure to update through this post you once it's resolved.
This is a completely new environment so please let me know if you are experiencing any other issues so we can correct them as soon as possible.
更多推荐
发布评论