fix paypal IPN postback response parsing #194
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ected HTTP headers
|
Whats the status of this? Has it been tested ... can it be merged? |
|
Hey there, a customer of mine got this mail from paypal too and I've checked this issue. After changed the code and tested again everything works fine now. |
|
that means we have 2 approves and can merge it now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not sure where this fix first came from, I've seen it posted on a few different blogs and forums.
The IPN class always expects a status code to be on the second line of the response, but curl sometimes adds extra HTTP headers, so it is better to look for the status code on the last line of the response instead.