Use history.replaceState instead of pushState on the initial page load. Also, your first history state change is missing a / causing a second state change:
I really like Ngrok because it also comes with a light-weight web client that lets you see requests and replay them. Replaying especially is huge for me when doing testing.
Nice! Some services don't allow non-https URLs for the webhook even for development (slack...), so might be nice to support that. Let's Encrypt provides free SSL certs if you wanted to go that route.
One thing I've wanted on tools like this is an API to query what requests have hit your particular endpoint which would be useful for unit testing applications which use webhooks.
Great work fredsted. I especially like how you can have multiple people use the same endpoint.
https://tailtub.com/ is a similar project I've been moonlighting on. It's a go binary and it's like Requestb.in but for stdin.
I wanted something where I didn't have to use a UI to start a stream. Your project and others like this I think are especially useful for giving API consumers more insight on what's happening to a resource after a record is queued (say after a HTTP 201).
38 comments
[ 4.9 ms ] story [ 87.9 ms ] threadEdit: Fixed.
Unaffiliated, just used recently and am big fan!
I really like Ngrok because it also comes with a light-weight web client that lets you see requests and replay them. Replaying especially is huge for me when doing testing.
Or use http://blog.runscope.com/posts/monitor-your-webhook-workflow...
Let's you transform input data with jq and redirect the webhook to another endpoint. Kind of make-your-own Zapier.
Also featuring replays.
The problem is that it is only good if you happen to know jq[1]. If you know a lot of jq you can do a lot of interesting things.
[1]: https://stedolan.github.io/jq/manual/
https://tailtub.com/ is a similar project I've been moonlighting on. It's a go binary and it's like Requestb.in but for stdin.
I wanted something where I didn't have to use a UI to start a stream. Your project and others like this I think are especially useful for giving API consumers more insight on what's happening to a resource after a record is queued (say after a HTTP 201).
Some other headers are not coming through, e.g. `te: gzip, deflate`
Otherwise, trying to use HTTPS instead of HTTP takes me to "Simon’s Filedump"
https://github.com/kdaigle/hookable
When you make a request with a non-supported HTTP verb, you get the full Laravel error message back instead of just an empty 405.
Are you disallowing verbs on purpose?