1. First, the browser will request DNS to resolve this domain name into the corresponding IP address.
2. Then, find the corresponding server on the Internet according to this IP address, establish a socket link, and send an HTTP Get request to the server. The server decides to return the default data resource to the visiting user.
3. There are actually complex business logic on the server side: there may be multiple servers, and which server is designated to handle the request. This requires a load balancing device to evenly distribute the requests of all users.
4. Whether the requested data is stored in a distributed cache or a static file, or in a database.
5. When the data returns to the browser, the browser parses the data and finds that there are some static resources (css, js or pictures) and initiates another HTTP request, and these requests may be on the CDN, then the CDN server will Process this user's request.
6. When the browser parses the html file, it will encounter and
No matter how the network architecture changes, there are always some fixed principles that need to be followed:
1. All resources on the Internet must be represented by a URL, which is a uniform resource locator.
2. It must interact with the server based on the HTTP protocol.
3. Data display must be carried out in the browser.
https://www.jianshu.com/p/558455228c43