So I've got a dev IIS server running on the intranet with a fixed IP. I've got a few applications setup in IIS.
I get the strangest behavior: If I load a page with IP address or server name & 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. It does this for several different apps, and each one does the same thing but with random IPs. 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.
If I deploy the same apps to an external facing server with proper domains/DNS they work fine.