This library facilitates writing Servant routes that can safely act as GitHub webhooks.
- Dispatching to routes based on the type of repository event.
- Automatic verification of request signatures.
- Route protection expressed in the type system, so webhook routes and regular routes cannot be confused.
Why use servant-github-webhook?
A webhook server needs to be publicly hosted. How can legitimate requests sent by GitHub be distinguished from (malicious) requests sent by other clients?
When a webhook is configured on a repository, a secret key is added. This key is used by GitHub to compute a signature of the request body that it sends; this signature is included in the request headers. The routing combinators in servant-github-webhook compute the signature of the received request body using the same key, and check that the signature in the request headers matches. If it does, then the request is legitimate.