<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Oshioregbeme Collins Inaboya on Medium]]></title>
        <description><![CDATA[Stories by Oshioregbeme Collins Inaboya on Medium]]></description>
        <link>https://medium.com/@inaboyacollins?source=rss-14699731c1f7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lCzrYQ6Qrtrt4ZmOlaIvYA.jpeg</url>
            <title>Stories by Oshioregbeme Collins Inaboya on Medium</title>
            <link>https://medium.com/@inaboyacollins?source=rss-14699731c1f7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:09:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@inaboyacollins/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What happens when you type “https://www.google.com" in your browser and press “Enter”]]></title>
            <link>https://medium.com/@inaboyacollins/what-happens-when-you-type-https-www-google-com-in-your-browser-and-press-enter-5e42b2836e45?source=rss-14699731c1f7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e42b2836e45</guid>
            <dc:creator><![CDATA[Oshioregbeme Collins Inaboya]]></dc:creator>
            <pubDate>Mon, 17 Apr 2023 23:34:37 GMT</pubDate>
            <atom:updated>2023-04-18T00:51:52.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PT79NEell4Vh6ACEhdnPGQ.gif" /><figcaption>Fig: Resolving google.com</figcaption></figure><p>When you type the website “https://www.google.com&quot; into your browser and hit Enter, a series of events takes place that results in the display of Google’s search engine on your screen. In this blog post, we will walk through the steps involved in this process and the different components involved.</p><p><strong>DNS Request:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*-O2gx1AOgGF3W5_3DTw5LA.jpeg" /><figcaption>Fig: DNS resolving route</figcaption></figure><p>The first step in the process is the Domain Name System (DNS) request. The DNS is responsible for translating human-readable domain names (e.g., <a href="http://www.google.com/">www.google.com</a>) into IP addresses that machines can use to communicate with each other. When you type in “https://www.google.com&quot;, your browser sends a DNS request to a DNS server to obtain the IP address associated with the domain name. The DNS server responds with the IP address, and the browser can then proceed to connect to the server.</p><p><strong>TCP/IP:</strong></p><p>With the IP address obtained from the DNS server, the browser initiates a Transmission Control Protocol (TCP) connection to the web server hosting the Google website. TCP is a protocol that governs the establishment of a connection between two devices and ensures reliable delivery of data. Once the connection is established, the browser can send a request to the server to retrieve the Google website’s content.</p><p><strong>Firewall:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*BUVC33rbe8ndmnq7O-p0HQ.jpeg" /><figcaption>Fig: Firewall Action</figcaption></figure><p>Before the request reaches the web server, it may have to pass through a firewall, which is a security measure designed to protect networks from unauthorized access. The firewall checks the request to ensure that it meets specific security criteria and then either allows or blocks the request.</p><p><strong>HTTPS/SSL:</strong></p><p>When the browser sends a request to the server, it includes a protocol called HTTPS (Hypertext Transfer Protocol Secure). HTTPS is a secure version of the standard HTTP protocol that encrypts data in transit between the browser and the server, making it difficult for attackers to intercept and read sensitive information such as passwords and credit card numbers. HTTPS uses SSL (Secure Socket Layer) to encrypt data in transit, and the browser and server must establish an SSL connection before any data can be exchanged.</p><p><strong>Load-balancer:</strong></p><p>Once the SSL connection is established, the request is sent to a load-balancer. A load-balancer is a device that distributes incoming network traffic across multiple servers to ensure that no single server becomes overwhelmed. The load-balancer checks the request’s destination and forwards it to one of the many available web servers capable of processing it.</p><p><strong>Web Server:</strong></p><p>The web server receives the request and begins processing it. It may use various programming languages, such as PHP or Ruby, to generate dynamic content that responds to user requests. The server retrieves the required data from the database and sends it back to the browser as an HTTP response.</p><p><strong>Application Server:</strong></p><p>In some cases, the web server may send the request to an application server. An application server is a server that hosts business logic and processes data on behalf of clients. The application server processes the request and returns the results to the web server, which then sends the HTTP response back to the browser.</p><p><strong>Database:</strong></p><p>Finally, the web server retrieves any necessary data from the database. The database stores data such as user profiles, search history, and other information required by the application. The web server retrieves the relevant data and sends it back to the browser as an HTTP response.</p><p>In conclusion, when you type “https://www.google.com&quot; into your browser and hit Enter, a series of events takes place. First, a DNS request is made to obtain the IP address associated with the domain name. Once the IP address is obtained, a TCP connection is established between the browser and the web server. Before the request reaches the web server, it may have to pass through a firewall, and the request must be sent over a secure HTTPS/SSL connection. The request is then sent to a load-balancer, which distributes incoming traffic to available web servers. The web server processes the request and may send it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e42b2836e45" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>