Scribd
Upload
9 views2 pages

How Browsers and Requests Work

fd

Uploaded by

Elie Al-Hallak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
9 views2 pages

How Browsers and Requests Work

fd

Uploaded by

Elie Al-Hallak
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Welcome to “How Browsers and Requests Work.

” After watching this video, you will be


able
to: Analyze the steps involved in loading a web
page. Describe the Domain Name System (DNS), and
Recall the process of DNS lookup in translating domain names into IP addresses.
Have you ever wondered how web browsers work
behind the scenes? Understanding this process
will help you understand web page loading. Let’s explore the steps involved. The
user interface is the first thing you
notice when you open a browser. Browsers provide a graphical user interface
(GUI). This interface allows users to interact with
different functionalities, such as navigation buttons, the address bar, bookmarks,
and settings. The address bar is for entering a website’s
URL (Uniform Resource Locator). After you enter a URL, the browser needs to
convert it into an IP (Internet Protocol) address using DNS (Domain Name System).
It requests a DNS server to resolve the domain
name into its corresponding IP address. After obtaining the IP address, the browser
connects with the web server using HTTP (Hypertext Transfer Protocol). This
connection involves sending an HTTP request
to retrieve the web page you requested. The browser sends an HTTP GET request to
fetch
all necessary resources for displaying the web page, including HTML files, CSS
stylesheets,
JavaScript files, images, and more. The web browser processes the request and
sends back an HTTP response containing the requested resources and metadata like
status
codes and headers. After receiving the response, the browser
starts the rendering process. The process involves parsing and interpreting
the HTML code and creating the Document Object Model (DOM). The browser applies CSS
rules from external
stylesheets to style each element in the DOM and executes any JavaScript code on
the web
page. After parsing HTML, CSS, and JavaScript, the
browser lays out the web page by determining element position, size, and style. It
then renders all elements on the screen
according to their styles. With the completion of rendering, the fully
loaded page becomes visible in the browser window. However, some resources may
continue loading. Browsers also manage user interactions like
clicking links, submitting forms, and running scripts triggered by mouse or
keyboard events,
responding with appropriate actions. Browsers also use caching techniques to store
local copies of web resources. This technique speeds up subsequent visits
to the same website since the browser retrieves the cached resources from local
storage instead
of making another round trip to fetch them from the server. Lastly, browsers
incorporate various security
measures to protect users from potential threats. The Domain Name System (DNS) is a
directory
that translates human-readable domain names into IP addresses, making it easier for
users
to access websites and online services. When users enter a web address, their
browser
initiates a request to a DNS server, asking it to convert the domain
name into the corresponding IP address. This conversion allows the browser to
establish
a connection with the desired website. The DNS system operates using a hierarchical
structure. The root servers function as the top level
of the hierarchy. These servers maintain information about the
top-level domain names such as .com, .net, .org, and so on. Below the root servers
are the top-level domain
(TLD) servers responsible for specific domain extensions. When a user enters a URL
into their web browser,
the device sends a request to a local DNS resolver. The user’s Internet Service
Provider (ISP)
provides this resolver, an intermediary between the device and the DNS
infrastructure. If the local resolver lacks the requested
IP address in its cache, it initiates a recursive resolution process. It contacts a
root server
that provides information about the relevant TLD server based on the domain
extension in the URL. The resolver then queries the appropriate
TLD server, such as the .com TLD server, for the domain “example.com.” The TLD
server responds with information about
which authoritative name server holds the records for the requested domain. The
local resolver then
queries these authoritative name servers to retrieve the specific IP address
associated with the requested domain. The resolver caches the received IP address
for faster resolution of subsequent requests for the same domain. It returns the IP
address
to the device, establishing a connection with the appropriate server hosting the
requested website. DNS records have a Time-to-Live (TTL) value
determining how long the resolver can keep them cached. After this duration
expires, the resolver
must perform another lookup to ensure it has up-to-date information. In this video,
you learned that:
Browsers have a user interface that allows interactions with various
functionalities,
such as navigation buttons and bookmarks. DNS translates domain names into IP
addresses,
enabling access to websites and online services. Web requests involve DNS
hierarchy, request
initiation, recursive resolution, TLD server contact, and authoritative name server
query
to retrieve IP addresses. DNS lookup includes recursive resolution,
contacting root and TLD servers, querying authoritative name servers, caching IP
addresses,
using TTL values.

You might also like