头部显示在Apache错误日志(卷曲和贝宝)

问题描述:

我刚刚注意到在我的错误日志中,每当我向PayPal API发出请求(使用php + curl)时,一些返回的头文件显示在我的Apache错误日志(不访问日志)。据我所知,这个特殊的要求从一开始就已经填满了我的日志(几个月后),但我第一次注意到它。现在我知道这不是什么大问题,但是我很乐意摆脱这个问题,因为这样可以更轻松地解决其他问题。头部显示在Apache错误日志(卷曲和贝宝)

首先,这里是错误提示:

[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * About to connect() to api-3t.paypal.com port 443 (#0) 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * Trying 66.211.168.126... * connected 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * Connected to api-3t.paypal.com (66.211.168.126) port 443 (#0) 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * SSL connection using DES-CBC3-SHA 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * Server certificate: 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * \t subject: /C=US/ST=California/L=San Jose/O=PayPal, Inc./OU=Information Systems/CN=api-3t.paypal.com 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * \t start date: 2009-09-24 00:00:00 GMT 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * \t expire date: 2011-09-19 23:59:59 GMT 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * \t issuer: /C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at https://www.verisign.com/rpa (c)09/CN=VeriSign Class 3 Secure Server CA - G2 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway. 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] > POST /nvp HTTP/1.1\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] Host: api-3t.paypal.com\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] Accept: */*\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] Content-Length: 217\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] Content-Type: application/x-www-form-urlencoded\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] \r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] < HTTP/1.1 200 OK\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] < Date: Thu, 17 Mar 2011 20:14:57 GMT\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] < Server: Apache\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] < Content-Length: 1162\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] < Connection: close\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] < Content-Type: text/plain; charset=utf-8\r 
[Thu Mar 17 15:14:19 2011] [error] [client 192.168.1.21] * Closing connection #0 

即使我让使用他们的示例代码的请求时,错误仍然显示。我甚至已经关闭了SSL_VERIFYPEER和SSL_VERIFYHOST curl选项,希望ssl(仍然有效)导致问题。我尝试了其他curl请求(不是通过ssl),并且它们不显示在错误日志中。

任何人都可以帮我找出问题吗?

尝试使用这种卷曲选项:

curl_setopt($ch, CURLOPT_VERBOSE,0); 
+0

这似乎很好地工作。感谢user470714。 – Brandon0 2011-03-21 22:47:43

是否使用CURLOPT_CERTINFO?如此描述:

TRUE在安全传输上输出SSL认证信息到STDERR

同时检查CURLOPT_VERBOSE,这对CURLOPT_CERTINFO启用在新的PHP版本的工作。

+0

欣赏信息。不幸的是,CURLOPT_CERTINFO需要5.3.2,我们实际上仍然在5.2.4上。 – Brandon0 2011-03-21 22:47:26

+0

这听起来像是他们将它从详细模式中分离出来,然后给出手动注释。很高兴知道! – Charles 2011-03-21 22:48:34