2
We have a web application that we deploy on either Win7 and Win10. The web client connects to apache and to our back-end server over HTTP and HTTPS. In one of our deployment scenarios, everything is deployed to a single PC (the localhost scenario). One of our testers noticed that on Win10 if he simply unplugs the PC's network cable, the web app is noticeably slower than when the cable in plugged in -- even though we're not actually going out on the network, we're just connecting to localhost. On Win7, with the exact same code and configs, the app is noticeably faster.
Does this make any sense to anyone? What would make Win10 slow down, but eventually work, when trying to access localhost when the network cable in unplugged?
thanks
--
2 additional pieces of information: (a) we have IPv6 disabled. (b) the speed difference when the network cable in unplugged is about 4 seconds. If a page would normally take say 1 second to come up; if the cable is unplugged, it will take 5 to come up. thanks
user3294765
Posted 2017-08-07T20:45:40.190
Reputation: 21
1Probably one simple answer: DNS. Has Windows had its hosts file to point your local install to "localhost", an IP or a named virtualhost (a domain name)? Addotionally, Windows 10 will look at IPv6 first so if you have a domain name or virtual host you'll need to set the hosts file to also have an IPv6 entry. – Kinnectus – 2017-08-07T20:53:22.077
With localhost interface apps talk to each other in same machine, hence the name loopback adapter. You can see that loopback packets with rawcap. See more at Wikipedia:localhost.
– Biswapriyo – 2017-08-07T21:00:21.5571Does the problem persist if you access
127.0.0.1instead of localhost? Is a proxy configured on the machine? Is there any software running on the machine that might intercept and inspect network connections that relies on an Internet connection to work, for example security software that checks URLs against an online database of bad websites? – I say Reinstate Monica – 2017-08-07T21:05:05.807