This repository was archived by the owner on Jul 20, 2020. It is now read-only.
[GCP] Use rawBody on IPN sample (fixes INVALID responses) #157
Conversation
This file contains hidden or 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
Salakar
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This example wasn't working out the box for addresses or names with special characters, all requests were coming back as
INVALIDunless they had no special characters.This issue relates to converting to JSON via express
body-parserand then trying to convert back to a raw string viaquerystring.As you can now access the raw body in GCP Functions (and Firebase) via
rawBody(docs), I've swapped outquerystringfor usingrawBodyinstead.Tested on my project and now works correctly without
INVALIDmessages.