From entering the URL in the browser to loading the page, the url page

From entering the URL in the browser to loading the page, the url page

The general meaning is: if there is a cache, it will be displayed directly. Otherwise, find the IP address on the local machine, find the IP address through DNS, and return it to the browser. Then, the browser communicates with the server over TCP, and the server returns data or error messages. Then render the data to the browser.

For example, if I want to open facebook.com, it is worth mentioning two points: one is that the web page may be redirected, such as from http://facebook.com to http://www.facebook.com. Second, the http GET request sent contains cookies.

You can customize the loading sequence of page images, audios, and videos to Increase the initial loading speed.

In addition, you can also consider the involve of the CDN (content delivery network ).

What are the advantages and disadvantages of using CDN?

• The disadvantages may be that it costs money, and it adds a bit of complexity to your deployment procedures.

• The main advantage is an increase in the speed with which the content is delivered to the users.

When en to use CDN?

• It will be most valid tive when you have a popular public website with some type of static content (images, scripts, css, etc ).

Is CDN a performance booster?

• In general, yes. when a specific request is made by a user, the server closest to that user (in terms of the minimum number of nodes between the server and the user) is dynamically determined. this optimizes the speed with which the content is delivered to that user.

In an extremely rough and simplified sketch, assuming the simplest possible HTTP request, no proxies and IPv4 (this wocould work similarly for IPv6-only client, but I have yet to see such workstation ):

1. Browser checks cache; if requested object is in cache and is fresh, skip to #9
2. Browser asks OS for server's IP address
3. OS makes a DNS lookup and replies the IP address to the browser
4. Browser opens a TCP connection to server (this step is much more complex with HTTPS)
5. Browser sends the HTTP request through TCP connection
6. Browser errors es HTTP response and may close the TCP connection, or reuse it for another request
7. Browser checks if the response is a redirect (3xx result status codes), authorization request (401), error (4xx and 5xx), etc .; these are handled differently from normal responses (2xx)
8. If cacheable, response is stored in cache
9. Browser decodes response (e.g. if it's gzipped)
10. Browser determines what to do with response (e.g. is it a HTML page, is it an image, is it a sound clip ?)
11. Browser renders response, or offers a download dialog for unrecognized types

Again, discussion of each of these points have filled countless pages; take this as a starting point. also, there are processing other things happening in parallel to this (processing typed-in address, adding page to browser history, displaying progress to user, notifying plugins and extensions, rendering the page while it's downloading, pipelining, connection tracking for keep-alive, etc .).

**************************************** **************************************** **************************************** **************************************** **********

First the computer looks up the destination host. If it exists in local DNS cache, it uses that information. Otherwise, DNS querying is already med until the IP address is found.

Then, your browser opens a TCP connection to the destination host and sends the request according to HTTP 1.1 (or might use HTTP 1.0, but normal browsers don't do it any more ).

The server looks up the required resource (if it exists) and responds using HTTP protocol, sends the data to the client (= your browser)

The browser then uses HTML parser to re-create document structure which is later presented to you on screen. if it finds references to external resources, such as pictures, css files, javascript files, these are delivered the same way as the HTML document itself.

Reference:

Http://stackoverflow.com/questions/2092527/what-happens-when-you-type-in-a-url-in-browser

Http://fex.baidu.com/blog/2014/05/what-happen/

When you open the browser, from entering a URL in the address bar to the entire page, what happened on the network

Open the browser, enter the URL, press enter, and you will find the router on the network. Find the router and read the route table. Theoretically, you can find the URL you entered in 12 route tables, and then empty link to this address. then, the default listening port 80 will be used. If it is an FTP header, it will listen to other ports for normal listening, and then it will shake hands, that is, determine the protocol type, and then session your computer like URL to submit the required information A form computer said I want you to address all the WEB pages under the WEB site will ask your computer to show your ID card to see if your computer is good. If it is good, say OK, I'll give it to you. however, I will give you a copy of the document on my WEB, which is cookies. At the same time, the WEB site calculates the webpage code into a window webpage acceptable to the user, and then your computer obtains this document. then, return the computed webpage to your browser based on the content in the document and the WEB.

This is probably the case.

What type of client-server interaction is involved in the process of inputting a URL in a browser and returning the webpage?

Man-Machine Interaction: client-server interaction