If so, have you updated to using HTTP 1.1 headers in the response back to PayPal? Along with the new HOST header? This is required by February 1 2013.

Any issues?

I'm having the following issues:

The "VERIFIED" final response back from PayPal takes minutes to come in after the header data for that response (it's supposed to come in instantly all at once).

PayPal will continually try to send me the same IPN messages. In other words it keeps repeating that IPN because it thinks it wasn't received/acknowledged.

On my IPN transaction list on PayPal's site, there's no response code listed while it's repeating. Successful IPNs all have a 200 code. This is especially odd because if PayPal is sending me the validation response, then it MUST have received my initial post-back. Arrrgh.

I've never used IPN, but trouble transitioning from HTTP/1.0 to 1.1 is usually trouble with persistent connections. If you don't want to support persistent connections, are you sending the "Connection: Close" header?

Peter

Thanks for the info Peter.

I'm not sure it helps yet with the live site, but it seems to get me on my way with the sandbox. If I don't include the close header, PayPal's sandbox test IPN process seems to get hung up (the web page will hang) and eventually tell me it couldn't connect. With the header it comes back immediately with a successful send and I do get everything back to my IPN listener.

Next up I had an issue that PayPal's sandbox itself was adding carriage return and newline to their response code for which the live site does not. Trimming whitespace fixed that and it seems to work.

Now I'm going to shut down the live site to external traffic and test this out there.

EDIT: Tested later the same day that it was OK and went live the next day. Has been working well ever since.

Here it is straight from the horse's mouth:



I forgot to mention that PayPal's PHP example also had a number of syntax errors.