I use Arch Linux, with KDE. I've spent the past TWO HOURS trying to get SpyJS -- a proxy-based JS debugging tool -- to work. It originally did not work, giving an incredibly vague 'No events captured' message, and no error. Because it's a proxy -- essentially a workaround for lack of proper integration -- it can't tell what's gone wrong, if it's on the browser's side.
So, modern browsers apparently try to 'intelligently' ignore proxy settings if you're accessing localhost. Did you know this? I sure didn't.
They do this silently with no warning anywhere -- even though they ostensibly do this for security reasons.
There's a workaround where you replace localhost with local
, and add local
to your /etc/hosts
. This workaround works for both Chromium and Firefox, in my tests, but gives you a 404 when you try to access the local dev server -- because SpyJS is paranoid and will reject it if it's accessing via the wrong domain.
If you want to use Chromium/Chrome, with localhost proxying you can _suppose