About Browser

What is Browser

Browser is vast space which allows you to write read text, files( png,mp3,mp4 etc.). It is a bridge between user and internet. It helps you to extract data or information from server and showcase that to you with less delay and readable output. Browsers work on mainly 3 web technologies i.e. HTML, CSS, JavaScript. All other languages uses libraries of this main languages.

What is http/http2/https

HTTP - Hypertext Transfer Protocol

This is a set of protocols which are used for transferring of Hypertext or Webdocs. This foundation of web browsers as browsers uses http to request and receive information. Also known as HTTP/1.1.

Some features of http are

• Stateless Protocol - This protocol means that each request is independent, meaning server don’t remember the user’s previous request and treat all request as new from scratch.

• Flexible - Http supports wide range of data types, allowing user to read share information without taking tension of file types it is in.

• Works on Client Server Based Model making browser client and website as sever

HTTP/2

• Version made in 2015 to fix limitations of HTTP/1.1

• Http2 can use multiplexing, means it can use send multiple files at same time. HTTP 1.1 can send or request or handle only file per TCP connection but HTTP2 solves this issue

• It uses compression meaning that it reduces the size of data before sending so this increases loading speed and file transfer is fast

• All http2 uses encryption, same as https (this means that the data is encrypted before sending which reduces chances of hacking or information leakage.

Fun Fact - Many servers don’t use encryption in transfer of data internally as it saves cost and because data is transferred internally there are no chances of its leak.

Working of Browser

Now lets discuss about working of Browser, how browser and server work together

• The working of browser mainly includes back and forth of data with server

• The flow is like browser takes the input eg. google.com

• To show result, browser needs ip address and google.com is not a ip address.

• In this case the request is sent to DNS server to find ip address of the url and the process is of getting ip address is also interesting.

• At first the the DNS server request the ip address of TLP (Top Level Domain) [Some eg of top level domains are .com .ac .in….]

• This request is sent from DNS server to Root server.

Fun Fact - There are only 13 root servers in world…All the requests from world wide web arrives at one of the root server depending of location of search.

• This back and forth happens between the DNS server and the Root server until the complete IP address of the URL is received.

• A question can be that if every search this process happens than how can browser access the URLs so quickly, the answer to this is that after a search the IP address is stored in cache so next time you enter google.com before shutting your laptop the server does not repeats the process completely, rather that result is store in cache and from that the IP address is extracted.