1. The client’s browser divides the URL into the diff. parts dividing including address, path name and protocol.
  2. DNS translates the domain name into the corresponding IP address. The numeric combination represents the site’s true address on the internet.
  3. The browser now decides which protocol used. A protocol in common parlance is a language in which the client’s to communicate with the server. FTP and HTTP are some such protocols.
  4. The server sends a GET request to the web server to retrieve the address it is given. It verifies the given address exists, and finds necessary files. Runs appropriate scripts exchanges cookies if necessary, and returns back to the browser.
  5. The browser now converts the data into HTML and displays results to the user. If it does not locate it sends an error message to the browser and to the client.

For any help contact bodHOST technical support staff.

Popular Posts You May Read

Explore more hosting insights, tips and industry updates.

Zen Cart Shopping Cart – Features and Setup Guide

Zen Cart Shopping Cart is a flexible open-source eCommerce solution that makes online selling simple,…

How to Fix DNS_PROBE_FINISHED_NXDOMAIN Error in Android

The DNS_PROBE_FINISHED_NXDOMAIN error on Android appears when your device is unable to resolve a domain…

How-do-to-Set-up-Nginx-as-a-Reverse-Proxy-in-Plesk.png

How to Set up Nginx as a Reverse Proxy in Plesk?

In this post, we’ll show you how to set up Nginx as a reverse proxy…