title: IISNode running Node.js with multiple domains issue
body: <p>I put a basic, no frills node npm-express blog site up on a azure website and the IIS load balancing or just iisnode itself seemed to cause issues running the app.js. Running outside of IIS didn't experience any issues. No websockets, just express using vash templates.</p>
  
  <p>The issues I ran into are:
  Using web deploy and some node_modules intermittently not deploying. npm lwip for instance would work at first then wouldn't if deploying again.  Sometimes other js and vash files would not update also.</p>
  
  <p>When using the site there was a plain vash templates section (the public facing side) and a login side of the site. The simple one page public facing side would intermittently create a 500 error. One out of every three request would do this. No logs generated and all logging was turned on. The error was from iisnode and not node itself. </p>
  
  <p>Using visual studio 13 with all the latest updates, remote debugging simply didn't work. Basically in the dark. Oddly the logged in portion using npm-passport-local worked but that never changed domains when using. It was only the pages on the public side that this would happen. FYI, the public side had multiple domains and various sub domains pointing to the site. All entered correctly in the azure portal and would work with the intermittent 500 error.  The page had links to other blogs with full urls, hence the domain would change. Which should be an issue but I suspect had something to do with it.</p>
  
  <p>I ended up having to create a azure vm and install node on it myself to get the site working without the use of IIS. FYI, running the node site locally on my sand I never encountered any issues either.</p>
  
  <p>Has anyone else experienced issues like this using iisnode and did you find a work around for this?
  I suspect it may happen when multiple domains are used for the same instance.</p>