How HTTP Requests are handled

Before a HTTP request is handled and sent to the web server, first of all a resolution of the IP address is gotten from the DNS server which practically is the work of the Authoritative Domain Name Server. When the resolved IP along side a cache data is saved to the browser's cache memory, a request is then created in the form of a datagram containing the request type, the IP address of the client's workstation. Also note that the client's PC connects to the internet using the TCP/IP protocol, the HTTP request is then sent through and the internet to the Load balancer. But this will not fly because google automatically routes any HTTP request "http://www.google.com" through a secured channel to eradicate eavesdropping and secured data. So automatically your HTTP response will be routed through the HTTPS secured protocol and your request will be encrypted using the SSL/TLS encryption protocol.

The load balancer receives the encrypted request and then channel it to a webserver available to handle and process the request. Know that Google's load balancer works also with proximity and location, so a request made in Nigeria for instance will be routed to a google web server in Nigeria. That is why when you make a HTTP request in Nigeria to "http://www.google.com" you could be automatically redirected to "https://www.google.com.ng"

My contribution to this matter can be found using https://sampulcodemine.hashnode.dev/what-happens-when-you-type-wwwgooglecom-in-your-browser-and-press-enter