Instant Payment Notification change from PayPal

[Hendrik]

Just in from PayPal -

_________________________________

To improve our site’s performance, scalability and availability, we’re going to expand the number of IP addresses for www.paypal.com. We announced this in a bulletin on October 18, 2011. As part of this expansion, we’ll discontinue support for the HTTP 1.0 protocol on February 1, 2013.

If your IPN (Instant Payment Notification) or PDT (Payment Data Transfer) scripts use the HTTP 1.0 protocol, this change may impact your ability to perform IPN post-back validation or PDT posts to www.paypal.com.

Additional Details

Starting February 1, 2013, we’ll require all incoming requests to have a “Host” header which complies with HTTP 1.1 specifications. This header was not required with the HTTP 1.0 protocol. 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

If your IPN (Instant Payment Notification) or PDT (Payment Data Transfer) scripts use the HTTP 1.0 protocol, you’ll need to update your scripts to HTTP 1.1, and include the “Host” header in the IPN postback script.
_________________________________________

When PayPal made an unannounced change the other year, the Instant Payment Notification (IPN) system stopped working for us and quite a few other people, until we made a Perl upgrade at the server.

Does anyone know if this is going to impact the SellerDeck software at all?

Hendrik

[Golf Tee Warehouse]

I received this email this morning also, at least thay have announced the change in advance which is unusual for Paypal.

[Krithika]

Hello

I will pass this on to my colleague in development and post back an update.

Regards

[guccij]

Any word on this Krithika? PayPal have updated their info to this:

"This is a follow-up to the bulletin we sent on 6 September, 2012. It has come to our attention that some merchants were experiencing issues getting their IPN scripts updated to use HTTP 1.1 because the scripts would get "hung" or take a long time to get a ‘VERIFIED’ response. We are including instructions on how to remedy this issue by adding a "Connection: close" header in the HTTP request.

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 the 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 the 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.1 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: www.paypal.com" and "Connection: close" HTTP headers in the IPN and PDT scripts.

For examples, please refer to https://www.x.com/node/320404.

The PayPal Sandbox has been configured to reject any HTTP requests without the "Host" header with a 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 https://www.paypal.com/pdt and https://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"

[Krithika]

Hello Jules

We are already working on testing the required changes and will post an update once we have confirmed the success of the same.

Regards

[Barry]

Hello Jules

We are already working on testing the required changes and will post an update once we have confirmed the success of the same.

Regards

Hi guys

Is there any update on this? I see the above post was back in September.

Thanks

[guccij]

And there was another email reminder from PayPal today:

Reminder: Update your IPN/PDT Scripts

This is a reminder to the bulletin we sent on 20 September, 2012. It has come to our attention that some merchants were experiencing issues getting their IPN scripts updated to use HTTP 1.1 because the scripts would get "hung" or take a long time to get a ‘VERIFIED’ response. We are including instructions on how to remedy this issue by adding a "Connection: close" header in the HTTP request.
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 the 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 the 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.1 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.

Your Action Required before February 1, 2013 You will need to update your IPN and/or PDT scripts to use HTTP 1.1, and include the "Host: www.paypal.com" and "Connection: close" HTTP headers in the IPN and PDT scripts.

For examples, please refer to https://www.x.com/node/320404.

The PayPal Sandbox has been configured to reject any HTTP requests without the "Host" header with a 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 https://www.paypal.com/pdt and https://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

[Krithika]

Hello

The required changes are going into and being tested in SD 2013. For earlier versions, we'll be notifying users well in advance re whether the changes will be in the form of a new PSPSetup file or instructions in the Knowledge Base.

Regards

[feemish]

Will these changes affect paypal express as well as paypal website payments standard?

[feemish]

Only about 3 weeks away from this big paypal change...

any news regarding what we should be doing about it?

[Krithika]

Hello Mark

The change has already been implemented in SellerDeck 2013 and we will soon provide a fairly simple fix for earlier versions before end next week.

Regards

[feemish]

Thanks Krithika.

[feemish]

The change has already been implemented in SellerDeck 2013 and we will soon provide a fairly simple fix for earlier versions before end next week.

its now the beginning of the week after that.. little bit worried becasue we are getting close to the Paypal change date now..

[guccij]

Fix has been posted already ...

[Krithika]

The fix is here.

Regards