I don't use Windows, so I'm confused about what is listening on 192.x.x.x:80 and 127.0.0.1:80. If there is some kind of layer 7 reverse proxy (in IIS, apache,

I don't use Windows, so I'm confused about what is listening on 192.x.x.x:80 and 127.0.0.1:80. If there is some kind of layer 7 reverse proxy (in IIS, apache, or some other software) listening on the public addresses, why does it matter which port, or even which localhost 127/8 address, is being listened on by the backend servers? Just have IIS listen on 8080 and apache on 8081, and then {internet} => {ext IP 192.0.0.x = reverse proxy} => {127.0.0.1:8081 = apache, 127.0.0.1:8080 => iis7} If you really want to browse those locally, from the server, using the names iis7.foo.com and apache.foo.com, then I can see using addresses in 127/8 and adding the entries to the HOSTS file, but this doesn't seem to be that valuable of a feature.