CareerCup

The first step is the DNS (Domain Name Server) lookup. It uses the DNS servers specified in your network settings (or given to you by DHCP) to lookup the top domain (cnn.com) and then ask that domain's nameserver for the IP address of the subdomain specified .

After it has the IP address, your browser begin communications with the web server. This is done using the specified protocol (which usually defaults to HTTP 1.1). A 'GET' request for '/' is made to the server, which responds with the HTML document contents and the appropriate headers (which tell the browser of the document's content-type, HTML, and other information). Then the browser parses the document and finds any URLs which it needs to embed in the page (like images or linked stylesheets) and does GET requests on each of those.

The browser also usually automatically makes a GET request for '/favicon.ico' (to display the little CNN icon next to the site title).

Your browser will also likely specify in its request headers that it wants the response content to be compressed, using the gzip algorithm. This makes the file download much smaller, if the server supports it. This is all transparent to you, even though it's like downloading a ZIP file and unzipping it.

When you reload the page, your browser checks if that page is already cached in your system, and if so, it does an HTTP request just for the header of the document, and checks its modified date. If this date is later than its cached copy, it requests the full document contents again and refreshes the page. Otherwise it just uses your local copy.

what exactly made u think this is a database question?

no this is not a data base question

Actually what happens that
when you enter the ulr first work is to find out the ip address of that which will be done by DNS naming ... then find the ip address

Browser splits what you type (the URL) into a hostname and a path.
Browser forms an HTTP request to ask for the data at the given hostname and path.
Browser performs DNS lookup to resolve the hostname into an IP address.
Browser forms a TCP/IP connection to the computer specified via the IP address. (This connection is actually formed out of many computers, each passing the data along to the next.)
Browser sends the HTTP request down the connection to the given IP address.
That computer receives the HTTP request from the TCP/IP connection and passes it to the web server program.
Web server reads the hostname and path and finds or generates the data that you've asked for.
Web server generates an HTTP response containing that data.
Web server sends that HTTP response back down the TCP/IP connection to your machine.
Browser receives the HTTP response and splits it into headers (describing the data) and the body (the data itself).
Browser interprets the data to decide how to display it in the browser - typically this is HTML data that specifies types of information and their general form.
Some of the data will be metadata that specifies further resources that need to be loaded, such as style sheets for detailed layout, or inline images, or Flash movies. This metadata is specified again as a URL, and this whole process repeats for each one until all are loaded.