Community Forums 

Main Content

Re:PayPal HTTP 1.0 Protocol email

    Sep 12 2012 21:17:13

    #1

    shactrack

    Join date : 2011-09-01      Posts : 28

    Yea I was about to ask the same thing. Sometimes there seems to be some lag time from the completion of a sale to it coming to my email...only more recently though (like the past week). I thought maybe this could've been why.....guess not...here's the full email I received.

    ACTION REQUIRED
    Dear XXXXX,

    In a bulletin dated October 18, 2011, we announced that we were going to expand the number of IP addresses for www.paypal.com to improve our site’s performance, scalability and availability. As part of this transition, we planned to discontinue support for HTTP 1.0 protocol starting February 1, 2013.

    We have recently identified that this change may impact the ability of some of our merchants to perform IPN (Instant Payment Notification) post-back validation or PDT (Payment Data Transfer) posts to www.paypal.com. This happens when the IPN or PDT scripts use HTTP 1.0 protocol and do not include the “Host: www.paypal.com” header in the HTTP request.

    Additional Details
    Starting February 1, 2013, we will require all incoming requests to have a “Host” header which complies with HTTP 1.1 Specifications. This header was not required under HTTP 1.0. IPN and PDT scripts using HTTP 1.0 may start failing with “HTTP/1.0 400 Bad Request” errors after February 1, 2013, which will result in IPN messages not being validated successfully, or PDT scripts not being able to retrieve transaction information.

    Action Required before February 1, 2013
    Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” header in the IPN postback script.

    Example:

    ASP
    //Set values for the request back
    req.Method="POST";
    req.Host="'www.paypal.com'";
    req.ContentType="application/x-www-form-urlencoded";

    Perl
    $req=HTTP::Request->new('POST', 'https://www.paypal.com/cgi-bin/webscr');
    $req->content_type('application/x-www-form-urlencoded');
    $req->header(Host=> 'www.paypal.com');

    PHP
    // post back to PayPal system to validate
    $header .="POST /cgi-bin/webscr HTTP/1.1\r\n";
    $header .="Content-Type: application/x-www-form-urlencoded\r\n";
    $header .="Host: 'www.paypal.com\r\n';;

    Java
    HttpsURLConnection uc=(HttpsURLConnection) u.openConnection(); uc.setDoOutput(true);
    uc.setRequestProperty("Content-Type","application/x-www-form-urlencoded"); uc.setRequestProperty("Host",;'www.paypal.com';);

    The PayPal Sandbox has been configured to reject any HTTP requests without the “Host” header with HTTP 400 error. Merchants can use the Sandbox environment to certify the changes to their IPN and PDT scripts.

    For more information on PDT and IPN, please refer to http://www.paypal.com/pdt and http://www.paypal.com/ipn. For additional information or questions about this change, please contact PayPal's Merchant Technical Support team via https://www.paypal.com/mts.

    Sincerely,

    PayPal