If you've ever tried to debug a long sequence of redirects where one of them is a 200 response with an HTML form that automatically gets submitted via JavaScript (cough SimpleSAMLphp cough), you might have noticed, in frustration, that you can't see that response in the Chrome DevTools' network tab and, instead, you get this message:

Failed to load response data: No resource with given identifier found.

Chrome has a function called "getEventListeners", which you can use to see all event listeners on a specific element. Unfortunately, there is no such thing in other browsers.

There's a nice utility that you can use to kill a process based on the port it's listening to, so for example if you have a server listening on port 80, you can run $ fkill :80 and it will murder it.

Only problem, it's made using Javascript, but if you're OK with having Node and plain-text JS files in your bin folder, you can install it with $ npm install --global fkill-cli.