CapitalIQ Interview Question
ConsultantsCountry: India
Interview Type: Phone Interview
is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.
CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.
Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.
Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.
In an rough and simplified sketch, assuming the simplest possible HTTP request, no proxies and IPv4:
- coding.arya June 19, 20131. Checks link's URL part. If not empty take that URL to be feteched.
2. browser checks cache; if requested object is in cache and is fresh, skip to #9
3. browser asks OS for server's IP address
4. OS makes a DNS lookup and replies the IP address to the browser
5. browser opens a TCP connection to server (this step is much more complex with HTTPS)
6. browser sends the HTTP request through TCP connection
7. browser receives HTTP response and may close the TCP connection, or reuse it for another request
8. 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)
9. if cacheable, response is stored in cache
10. browser decodes response (e.g. if it's gzipped)
11. browser determines what to do with response (e.g. is it a HTML page, is it an image, is it a sound clip?)
12. browser renders response, or offers a download dialog for unrecognized types
There are many 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.).