Thanks for bringing this thread to my attention.
I see. I would suggest that you modify the script we provide just a bit ( included as attachment ).
Your central IPN handler can forge the PayPal IPN server's IP address, to make SalesForce think it came directly from PayPal's IPN server. The attached file is modified for you to make this work.
- Code:
$paypal_ipn_server_ip_address = $ip = "216.113.188.202";
header ("HTTP/1.0 200 OK") . exit (trim (curlpsr ($CONFIG[$domain], http_build_query ($_POST), 20, 20, array ("REMOTE_ADDR: " . $ip, "HTTP_X_FORWARDED_FOR: " . $ip))));
To answer your question ... no, this is not an issue for s2Member. s2Member does NOT check the originating IP address of the remote host; because, as you see here it can be forged anyway.
Instead, s2Member talks directly to PayPal, and s2Member verifies the contents of each IPN submitted to it; looking for verification directly from PayPal in the context of it's own routines. So, as long as your IPN did originate at PayPal (at some point), it's fine with s2Member. In short, you should be OK to do it the other way around, if you prefer. It is also possible to self-authenticate IPNs sent to s2Member, using a Proxy-IPN Key. Please check your Dashboard here ( screenshot attached ).
SNAG-0075.pngStatistics: Posted by Jason Caldwell — October 26th, 2011, 1:38 pm
]]>