Explain in detail the steps/processes, occur from the moment, type a URL in a browser and hit enter

In a extremely rough and simplified sketch, assuming the simplest possiblehttp request, no proxies and IPV4 (this would w Ork similarly for ipv6-onlyclient, but I had yet to see such workstation):

2. Browser checks cache; If requested object is in the cache and is fresh, skip to#9

4. Browser asks OS for server ' s IP address

6. OS makes a DNS lookup and replies the IP address to the browser

8. Browser opens a TCP connection to server (this step was much more

   Complex with HTTPS)

10. Browser sends the HTTP request through TCP connection

12. Browser receives HTTP response and may close the TCP connection, or

    Reuse it for another request

14. Browser checks if the response is a redirect (3xx result status codes),

    Authorization Request (401), error (4XX and 5xx), etc; These is handled

    Differently from normal responses (2xx)

16. If cacheable, response is stored in cache

18. Browser decodes response (e.g. if it ' s gzipped)

20. Browser determines-do with response (e.g. are it a HTML page, is it

    An image, was it a sound clip?)

22. Browser renders response, or offers a download dialog for unrecognized

    Types

Again, discussion of each of these points has filled countless pages; Take Thisas a starting point. Also, there is many other things happening in parallel to

This (processing typed-in address, adding page to browser history, displayingprogress to user, notifying plugins and Exten sions, rendering the page Whileit ' s downloading, pipelining, connection tracking for keep-alive, etc.).

Explain in detail the steps/processes, occur from the moment, type a URL in a browser and hit enter