Visiting weird ports with Chrome

As a security measure, Chrome doesn’t allow by default to visit any not known web port (eg not 80,443, 8080 etc).

I had to debug site hosted on port 102 so I made the following bat file to fire up Chrome and test the website:

cd "%AppData%\..\Local\Google\Chrome\Application"
chrome.exe --explicitly-allowed-ports=102

Note that AppData lands you to the Roaming profile, while Chrome installs (if you select to install it only on your account) in the Local folder.

Hope this helps.

Debugging a node.js app in windows (no eclipse)

If you don’t want to install eclipse and google dev tools to debug your node.js app you may use node inspector which is a node.js app that resembles google chrome’s dev tools. You start your node app passing the –debug-brk (or –debug if you don’t care about the first lines of code) and then fire up node inspector and debug the app. I actually have node inspector running all the time and I simply refresh the webpage when I reload the application.

Happy debugging…