[Heroku][AWS] handler not working because of url param rewritten about chathooks HOT 5 CLOSED

I checked with the proxy running locally and this error is only for the aws handler.
Looks like the aws api gateway is the cause of this error.

from chathooks.

The reason AWS doesn't work is that Lambda functions don't handle application/x-www-form-urlencoded requests provided by Heroku so the code needs to be modified for AWS.

Heroku now supports application/json webhooks so updating the Heroku handler to JSON will solve the issue for Heroku.

https://devcenter.heroku.com/articles/app-webhooks#receiving-webhooks

Heroku calls this version 3.

"version": "application/vnd.heroku+json; version=3"

I'll update / enhance to support the JSON webhook event format which should resolve this.

Wootric still uses a Ruby on Rails type webhook format so it needs to be supported for that: #15

from chathooks.

Here's some info on potentially overloading text/plain Content Type on AWS.

• https://stackoverflow.com/questions/31362195/output-plain-text-content-from-amazon-api-gateway-endpoint
• https://www.reddit.com/r/aws/comments/6219kx/api_gateway_non_json_inputs_textplain/

from chathooks.

Implemented in a3b406c

As of this commit, url param has been renamed to outputURL param. There is no fallback but multiple instances of Chathooks can be run during the roll over.

from chathooks.

v0.7.0 Released.

from chathooks.