Loopback 127.0.0.1 and how it pulls up xampp
Posted: 06. March 2015 09:58
I'm trying to visually understand something.
When I type the Loopback address 127.0.0.1 my browser, the browser points to http://127.0.0.1/xampp/ (as long as XAMPP is running)
I guess what I'm not able to visualize is, how does my browers know that it's suppose to loop itself to the XAMPP Apache server application? I know XAMPP's httpd.conf file contains the instructions responsible for directing the browser to pull up the XAMPP welcome page. But how does the loopback address on a local machine know to follow the commands in the httpd.conf file specifically? For example: What if I was running two servers each with their own config files on the same machine. How would the loopback address know which application server to listen to over the other?
When I type the Loopback address 127.0.0.1 my browser, the browser points to http://127.0.0.1/xampp/ (as long as XAMPP is running)
I guess what I'm not able to visualize is, how does my browers know that it's suppose to loop itself to the XAMPP Apache server application? I know XAMPP's httpd.conf file contains the instructions responsible for directing the browser to pull up the XAMPP welcome page. But how does the loopback address on a local machine know to follow the commands in the httpd.conf file specifically? For example: What if I was running two servers each with their own config files on the same machine. How would the loopback address know which application server to listen to over the other?