# # ### ## # # ### ### # # ## ### # # # # # ### ## # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ### ## ## ### # # # # ## ## ## # ### # # # # # ## ### # # # # # # # # # # # # # # # # # # # # # # # # # # ### ## # # ### ### # # # # ### ### # # # ### ### # # # #
┌────────────────────────────────────────────────────────────────────────────┐ │ WEBHOOKR.TXT .. issue #29 .. typed up by dr_pylon │ │ the last link in the chain │ │ host: webhookrelay.link last touched: 02/2001 │ └────────────────────────────────────────────────────────────────────────────┘
Webhook Relay Link: catch HTTP requests and look at them
Make a catcher (GET or POST, no account, no key):
curl https://www.webhookrelay.link/chain
The answer is a redirect to the page that shows what arrives; the URL to send to is in the body.
Whatever is sent to the first URL is kept, with any method, any path below it and any body:
curl -d 'hello' https://www.webhookrelay.link/link/<id>
curl -X PUT -H 'X-Test: 1' 'https://www.webhookrelay.link/link/<id>/some/path?a=b'
See what arrived, newest first:
https://www.webhookrelay.link/links/<id>
curl https://www.webhookrelay.link/links/<id>?format=json
curl https://www.webhookrelay.link/links/<id>?format=txt
Whatever arrives here stops here.
you are caller number 000002 or thereabouts.
04/10/00 rewrote the whole listing code at 4am. it is worse now but it is mine 15/05/00 somebody sent 9000 requests in a minute. respect, but why 04/03/00 moved the box to a new closet. uptime counter reset, sorry
TODO. there was one but it went away.
DuskOperator, elk/2, Baron Carrier, oxbow_lk, cinder.sys, zlotnik, everyone on the old board and the ones who still dial in. no greetz to whoever keeps portscanning the box.
end of line. -- dr_pylon [ top ] (c) 1999 Webhook Relay Link. copy this file freely, just don't change it. EOF