The very popular question being asked how exactly HTTPS work? A lot of blogs around it are available in detailed form as well as in shorter form. I will try to keep it in middle not lengthy nor short.
In my previous blog I covered the working of the browser How does the browser work?
I will start where I left earlier how HTTP works? HTTP stands for HyperText Transfer Protocol it is an application side protocol used for transmitting hypermedia documents like HTML. HTTP transfers data over TCP connection between client and server (Let’s not go in deep about it, we can add a new blog on it). HTTP transfers plain text over the connection which can be read by someone who has access to your connection. For example, if you are exchanging data over shared wifi one can sniff your data using sniffers(Will add a blog on how Wireshark can be used for sniffing the data). …
This question is very popular that whenever we type URL in browser what happens? The very popular answer is browser will look to resolve the DNS by looking into the caches (browser cache, if not found, system cache, if not found then in ISP cache). If all the cache lookups will fail then ISP providers will execute the domain name query. But what exactly happens in the background.
- When you type in www.abcd.com in your web browser it will first go to recursive resolver hosted with ISP(Internet Service Provider i.e. Prime Fibernet in my case) end (by default) or at another DNS(Domain name system) server you’ve configured. …
About
