Closed ryanwalls closed 8 years ago
Agreed - I'm guessing that's from some Velocity interaction as part of https://github.com/mweagle/Sparta/blob/master/resources/provision/apigateway/inputmapping_default.vtl. Will take a look.
@mweagle I tried this guy's template for url form encoded data, and it worked: http://stackoverflow.com/a/35068572/411229.
See his gist here: https://gist.github.com/ryanray/668022ad2432e38493df
It would of course need to be adapted to match the format sparta is looking for.
Thanks very much for tracking this down - will definitely help with the resolution & I'll work to get it included for the 0.9.0 release.
On Tue, Sep 6, 2016 at 2:50 PM, ryanwalls notifications@github.com wrote:
@mweagle https://github.com/mweagle I tried this guy's template for url form encoded data, and it worked: http://stackoverflow.com/a/ 35068572/411229.
See his gist here: https://gist.github.com/ryanray/668022ad2432e38493df
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mweagle/Sparta/issues/19#issuecomment-245107269, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYr6t0X3Hn9vfZY7GgUDBlN78gOAFznks5qneARgaJpZM4J2NDh .
matt weagle | mweagle@gmail.com
Should be resolved by https://github.com/mweagle/Sparta/commit/2782cdc0adbf0a3c4f18185f98857475c3f4fe50, available in v0.9.0.
Working through some examples and proof-of-concepts and hitting a problem with url form encoding an @ sign in a post parameter.
Our code for our lambda function:
Our post from postman:
The response (notice the body is printing
foo%!f(MISSING)oo.com
instead of foo@foo.com:Any ideas on what is happening? My assumption was that perhaps there is some translation issue in the integration mapping.