Question

昨天出现了麻烦 - 从curl获得以下答案（由curl_exec在php脚本中调用）：

$<errno>35</errno>
$<error>Unknown SSL protocol error in connection to w3s.webmoney.ru:443 </error>

该错误仅在有时发生，大约4-5个有效响应，一个无效，35错误。在昨天之前，应用程序正确地处理了这些请求很长一段时间。

希望有人会告诉我这个错误的可能原因。

P.S。我们最近遇到了互联网连接问题，是否能以某种方式与该错误相关联？

UPD： 将详细输出设置为true使curl写入以下日志：

* About to connect() to w3s.webmoney.ru port 443 (#0)
*   Trying 82.198.171.158... * connected
* Connected to w3s.webmoney.ru (82.198.171.158) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: ${path}/WebMoneyCA.crt
  CApath: /etc/ssl/certs
* SSL connection using RC4-MD5
* Server certificate:
*        subject: C=RU; O=WebMoney Transfer; OU=WebMoney Web Service; CN=w3s.webmoney.ru
*        start date: 2010-06-07 10:03:43 GMT
*        expire date: 2012-06-07 10:13:43 GMT
*        common name: w3s.webmoney.ru (matched)
*        issuer: OU=WM Transfer Certification Services; O=WM Transfer Ltd; CN=WebMoney Transfer Root CA
*        SSL certificate verify ok.
> POST /asp/XMLPurses.asp HTTP/1.1
Host: w3s.webmoney.ru
Accept: */*
Content-Length: 281
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 200 OK
< Date: Fri, 10 Dec 2010 13:00:04 GMT
< Server: Microsoft-IIS/6.0
< X-Powered-By: ASP.NET
< Content-Length: 4423
< Content-Type: text/xml; Charset=windows-1251
< Expires: Fri, 10 Dec 2010 13:00:04 GMT
< Set-Cookie: ASPSESSIONIDQADQDTAQ=FJMNECHBENFFAADHEHPFOKAE; path=/
< Cache-control: private
<
* Connection #0 to host w3s.webmoney.ru left intact
* Closing connection #0
* About to connect() to w3s.webmoney.ru port 443 (#0)
*   Trying 212.158.173.158... * connected
* Connected to w3s.webmoney.ru (212.158.173.158) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: ${path}/WebMoneyCA.crt
  CApath: /etc/ssl/certs
* Unknown SSL protocol error in connection to w3s.webmoney.ru:443
* Closing connection #0

UPD ：麻烦不在我们这边。问题隐藏在w3s.webmoney.ru，212.158.173.158服务器中。如果信息可用，我会添加有关该错误的更多详细信息。

Answer 1

得到WM支持人员的以下回复：

“主机名w3s.webmoney.ru上有四个IP地址。当请求最终在212.158.173.158上时，SSL正被提供商的一个反DDoS硬件杀死。问题是本地化的，他们'现在正试图修复它。“

卷曲错误35，可能的原因？

1 个答案: