Lautan Coding

There are times when you need to find out what background "ajax/web endpoint calls" a webpage is making under the covers. As it happens, the other day was one of those times! - I needed to find out which Web Endpoints an internal website was calling over an HTTPS connection. Now, we all know we could use Fiddler or the fantastic Wireshark for analysing network traffic but I didn't have either of these installed on the box I was using. I was just about to install Fiddler when I remembered chrome's internal net events page. Simply open chrome.exe and navigate to: chrome://net-internals/#events . It's like having Fiddler built into the browser. Now, go pack to your web page and perform your action (in my case it was clicking a button). The great thing about this is that it works over SSL/TLS connections which means you don't need to install a SSL certificate to decrypt your traffic. Okay, it's not as powerful as Fiddler or Wireshark , but, if a

Welcome to Client-Side tales from a Server-Side Developer. If your background is server-side development like me, then visiting the land of JavaScript can be quite daunting. Don't get me wrong, I'm not talking about the JavaScript language itself. Whilst the language has recently been updated to ES6 , I'm talking about everything else that comes along with it. Honestly, as an outsider looking in it's like the Cambrian Explosion out there. A soup of different language extensions, frameworks, plug-ins, package managers, task runners, et cetera, et cetera. Where do you start? So Many Questions As I dip my toe into today's JavaScript ecosystem, I want to make sure I'm as forward-leaning as possible. I don't want to be writing JavaScript from 1995! But after spending time reading the interwebs you come away with lots of questions. Questions such as: Do I really need to install Node.js , just to write JavaScript? What's the difference between