News for hackers. Stuff that matters.
Re:What webhooks are and why you should care by tptacek on Tuesday February 10, 2009 @11:15AM (#475348)
How would you do that? The point here is, the webhook call can't really know what it's POST'ing to; all it takes to set up a loop is another web app that will itself formulate an arbitrary POST.
Re:What webhooks are and why you should care by Xichekolas on Tuesday February 10, 2009 @12:17PM (#475492)
Just keep track of a 'url stack' in the POST message (assuming the post body is structured with something like JSON or XML). If a service detects a cycle it can drop the message or give back a 50x error or something.
Re:What webhooks are and why you should care by tptacek on Tuesday February 10, 2009 @04:51PM (#476037)
The problem here is that you can aim a "web hook" at any other HTTP endpoint, which may or may not honor any "web hook loop avoidance" protocol you come up with, and if that endpoint re-triggers the activity that generated the hook update, you have a loop.

HTTP is stateless, so the "url stack" idea is going to be tricky to implement.

Re:What webhooks are and why you should care by Xichekolas on Wednesday February 11, 2009 @12:03AM (#476559)
Yeah I suppose keeping a trail of breadcrumbs only helps you prevent accidental loops. A malicious service in the chain could just clear the stack and create a loop, and no one would be any the wiser.
Re:What webhooks are and why you should care by kragen on Wednesday February 11, 2009 @10:58AM (#477141)
A malicious machine that wants to DoS a server doesn't need web hooks in order to make a bunch of requests to the server. It can just run ab, the Apache Benchmark program.
Re:What webhooks are and why you should care by Xichekolas on Wednesday February 11, 2009 @02:04PM (#477417)
Presumably DoSing wouldn't be the objective here. If some of your services in the loop send SMS messages or modify your checkbook register, that would be much more annoying than a simple DoS.
Re:What webhooks are and why you should care by nx on Tuesday February 10, 2009 @11:21AM (#475364)
Maybe delaying subsequent POSTs from the same server, unless it's whitelisted, and Bayesing out fishy requests. That should reduce the load.