title: Visual Studio 2013: Debug using IP Address instead of LocalHost
body: <p>I have a WCF REST service which debugs and works perfectly when using IISExpress and this url:</p>
  
  <pre><code>http://localhost:&lt;portnumber&gt;
  </code></pre>
  
  <p>However, for various reasons, I need it to also work with IIS Express and THIS url:</p>
  
  <pre><code>http://&lt;ip address&gt;:&lt;portnumber&gt;
  </code></pre>
  
  <p>When I tried originally, I got HTTP error 400: Bad request.  Then I used google and ended up here: <a href="https://stackoverflow.com/questions/14725455/connecting-to-visual-studio-debugging-iis-express-server-over-the-lan">Connecting to Visual Studio debugging IIS Express server over the lan</a></p>
  
  <p>That thread asked the EXACT same question, and the answer got me part of the way there.  Following all the most excellent advice in that thread, I did the following:</p>
  
  <p><strong>Edit the IISExpress Host.config:</strong></p>
  
  <p>1: Open the %USERPROFILE%\My Documents\IISExpress\config\applicationhost.config file. </p>
  
  <p>2: Changed all 17 of these lines:</p>
  
  <pre><code>&lt;binding protocol="http" bindingInformation="*:8080:localhost" /&gt;
  </code></pre>
  
  <p>To look like this instead:</p>
  
  <pre><code>&lt;binding protocol="http" bindingInformation="*:8080:*" /&gt;
  </code></pre>
  
  <p>(the port number varied on all 17 lines)</p>
  
  <p><strong>Visual Studio:</strong></p>
  
  <p>Closed, re-opened but ran as admin</p>
  
  <p><strong>Windows Firewall:</strong></p>
  
  <p>Added the port in question to allow incoming connections</p>
  
  <p><strong>CMD:</strong></p>
  
  <pre><code>netsh http add urlacl url=http://*:XXXXX/ user=Everyone
  </code></pre>
  
  <p>Ran that command, where XXXXX is the port number.</p>
  
  <p>Now, when I start debug and go to this URL:</p>
  
  <pre><code>http://&lt;ip address&gt;:&lt;portnumber&gt;
  </code></pre>
  
  <p>Instead of "HTTP error 400: Bad request", I now get "HTTP Error 503. The service is unavailable."</p>
  
  <p>This is progress, as the browser is now at least hitting IISExpress, right?  But I'm not sure at this point how to get past this 503 error.  I've been searching google for that error for a while, but nothing is specific to what I'm trying to do.</p>
  
  <p>Any ideas?</p>