jstemmer / rehook Goto Github PK

Filter incoming requests to determine whether or not to perform an action. You should be able to create filters for request headers and body contents (e.g. match application/json content type with the body containing a certain key/value).

None of the stats are removed when a hook is deleted.

Make sure incoming requests are only from the service where you configured the webhook. Drop any invalid requests.

E.g. github includes a X-Hub-Signature header that is the SHA1 HMAC of the request body using a shared secret.

It should be possible to rate limit incoming requests. We could still accept them, but limit the number of actions taken in a certain time period.

Requests that exceed the limit could be ignored or aggregated for use in the next action.

or provide a way to undo the delete.

Define actions to take for incoming requests. For example, forward request, send new request, send email, store request, log request, etc.

Filter should halt the processing chain on errors, actions shouldn't.

There's a lot of duplication in the templates and component source files. Now that we've got some more components it's time for some refactoring.

Right now, most changes in the hook edit page are instant or require you to navigate to a different page. Ideally we should be able to add, edit and delete components on the hook edit page (without navigating away) and have a button to save the changes or cancel.

For example, send an email when there hasn't been any request in a certain time period for a configured hook.