Geek asks and answers

Headers appear in apache error log (curl and paypal)

I just noticed in my error logs that whenever I make a request to the PayPal API (using php + curl), some of the returned headers appear in my apache error log (and not in the access log). As far as I can tell, this particular request fills my journals from the very beginning (after a few months), but I just noticed it today for the first time. Now I know that this is not a big problem, but I will gladly get rid of it, as this will facilitate the elimination of other problems.

First, here are the error logs:

[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

, . curl SSL_VERIFYPEER SSL_VERIFYHOST , ssl ( ) . ( ssl), .

- ?

+3
2

cURL:

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

CURLOPT_CERTINFO? :

TRUE, SSL STDERR .

CURLOPT_VERBOSE, CURLOPT_CERTINFO PHP.

0
source

More articles:


All Articles