Developer confused by intranets =P
So I've got a dev IIS server running on the local network with a fixed IP. I've got a few applications setup in IIS bound to different ports.
I get the strangest behavior: If I load a page via IP address & port, it writes the correct response (as seen in my debugging proxy) but hangs with a white page for a long time while chrome says "waiting for" and it's an incorrect IP address unrelated to the server or application.
The browser actually tries to make a second request to a wrong IP, and it somehow manages to hold up the display of the page. Happens in FF and Chrome as indicated by Fiddler.
It does this for several different apps on different ports, and each one does the same thing but with a different incorrect IP for each one. It waits to connect to wrong local intranet IP. I pinged one, and it's not even an assigned IP on the network.
I can repeat this on a machine without a debugging proxy, and none of the incorrect IPs show up anywhere in the projects.
I'm not sure we even have a DNS server configured. We are a small company with no IT services. What I did was fix the IP address on the adapter of the server.
If I deploy the same apps to an external facing server with proper domains/DNS they work fine.