- browser checks cache; if requested object is in cache and is fresh, skip to #9
- browser asks OS for server IP address
- OS makes a DNS lookup and replies to browser
- browser opens a TCP connection to server (this step is much more complex with HTTPS)
- browser sends the HTTP request through connection
- browser receives HTTP response and may close the TCP connection, or reuse it for another request
- browser checks if the response is a redirect, authorization request, etc.; this is handled differently from normal responses
- if cacheable, response is stored in cache
- browser decodes response (e.g. if it's gzipped)
- browser determines what to do with response (e.g. is it a HTML page, is it an image, is it a sound clip?)
- browser renders response, or offers a download dialog for unrecognized types
Friday, May 6, 2011
what happens when you type in a URL in browser
Subscribe to:
Posts (Atom)