PayPal REST API:请求oauth令牌返回500 [英] PayPal REST API: Requesting oauth token returns 500

查看:93
本文介绍了PayPal REST API:请求oauth令牌返回500的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

两天前,我们的Paypal集成发生了问题.不幸的是,事实证明,尝试联系Paypal支持没有帮助(两天内没有回复),所以我会在这里尝试好运.

Two days ago, something broke with our paypal integration. Unfortunately, trying to contact paypal support has proven to be of no help (no reply in 2 days), so I'll try my luck, here.

请求令牌(curl https://api.paypal.com/v1/oauth2/token -H接受:应用程序/json" -H接受语言:en_US" -u"****:****" -d"grant_type = client_credentials")开始总是返回一个空响应,并且好吧,这是500个错误.

Requesting the token (curl https://api.paypal.com/v1/oauth2/token -H "Accept: application/json" -H "Accept-Language: en_US" -u "****:****" -d "grant_type=client_credentials") started ALWAYS returning an empty response and well, a 500 error.

请注意,使用api.sandbox.paypal.com和沙盒凭据也可以正常工作.

Note that the same works just fine with api.sandbox.paypal.com and sandbox credentials.

我仔细检查了我们的凭据,它们很好.还要注意,我使用的凭据并不重要,它始终返回相同的值-500.

I double checked our credentials and they are fine. Note as well, that it doesn't matter what credentials I use, it always returns the same - 500.

这是curl的输出... -v;看起来像内部服务器错误,如500所示:

Here's the output of curl ... -v; looks like you have an internal server error, as the 500 shows:

* About to connect() to api.paypal.com port 443 (#0)
* Trying 173.0.88.98...
* connected
* Connected to api.paypal.com (173.0.88.98) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: /usr/ssl/certs/ca-bundle.crt
CApath: none
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Request CERT (13):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using DES-CBC3-SHA
* Server certificate:
* subject: C=US; ST=California; L=San Jose; O=PayPal, Inc.; OU=PayPal Production; CN=api.paypal.com
* start date: 201
* expire date: 201
* subjectAltName: api.paypal.com matched
* issuer: C=U
* SSL certificate verify ok.
* Server auth using Basic with user '****'
> POST /v1/oauth2/token HTTP/1.1
> Authorization: Basic ****
> User-Agent: curl/7.27.0
> Host: api.paypal.com
> Accept: application/json
> Accept-Language: en_US
> Content-Length: 29
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 29 out of 29 bytes
* additional stuff not fine /usr/src/ports/curl/curl-7.27.0-1/src/curl-7.27.0/lib/transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 500 Internal Server Error
< Server: Apache-Coyote/1.1
< Date: Thu, 28 Mar 2013 15:59:53 GMT
< Content-Length: 0
< Connection: close
<
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):

谢谢!

推荐答案

这是当前正在研究的内容.如果您尚未使用PayPal MTS打开票证,建议您使用技术支持打开票证,因此您的问题可以添加到示例中.问题解决后,您还将收到通知.

This is something that is currently being looked into. If you have not already opened a ticket with PayPal MTS I would advise opening up a ticket with Technical Support, so that your issue can be added to the examples. You will also then be notified once the issue has been resolved.

修改:此问题已于格林尼治标准时间04:12 AM(31/03/2013)解决.

edit: This is now resolved as of 04:12 AM GMT (31/03/2013).

这篇关于PayPal REST API:请求oauth令牌返回500的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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