The process from entering URL to page loading?

1. From the browser receiving the URL to opening the network request thread
(this part can expand the mechanism of the browser and the relationship between the process and the thread)
2. Starting the network thread to issue a complete http request
(this part involves dns query, tcp/ip request, knowledge of the five-layer Internet protocol stack, etc.)
3. From the server receiving the request to the corresponding background receiving the request
(this part may involve load balancing, security interception and internal processing in the background, etc.)
4. Background and foreground HTTP interaction
(this part includes knowledge such as http header, response code, message structure, cookie, etc., can mention the cookie optimization of static resources, and encoding and decoding, such as gzip compression, etc.)
5. The caching problem that comes out separately, http Cache (this part includes http cache header, etag, catch-control, etc.)
6. The parsing process after the browser receives the http packet
(parse html-lexical analysis and then parse it into a dom tree, parse css to generate a css rule tree, Merge into a render tree, then layout, painting rendering, composite layer synthesis, GPU rendering, external resource processing, loaded and domcontentloaded, etc.)
7. CSS visual format model (elements rendering rules, such as containing blocks, control boxes , BFC, IFC and other concepts)
8.
JS engine analysis process (JS interpretation stage, preprocessing stage, execution stage to generate execution context, VO, scope chain, recycling mechanism, etc.)
9. Others (different knowledge modules can be expanded , Such as cross-domain, web security, hybrid mode, etc.)

Send an idea first, and the details will be updated later.

Guess you like

Origin blog.csdn.net/qq_42698576/article/details/108745805