<?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 Chidimma Blessing Onuora on Medium]]></title>
        <description><![CDATA[Stories by Chidimma Blessing Onuora on Medium]]></description>
        <link>https://medium.com/@onuorachidimma4?source=rss-761ed2af4b12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*urNiTuEImqLuICWz</url>
            <title>Stories by Chidimma Blessing Onuora on Medium</title>
            <link>https://medium.com/@onuorachidimma4?source=rss-761ed2af4b12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:29:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@onuorachidimma4/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[Decoding What Happens When You Type “https://www.google.com" in Your Browser and Press Enter.]]></title>
            <link>https://medium.com/@onuorachidimma4/decoding-what-happens-when-you-type-https-www-google-com-in-your-browser-and-press-enter-251168f53550?source=rss-761ed2af4b12------2</link>
            <guid isPermaLink="false">https://medium.com/p/251168f53550</guid>
            <dc:creator><![CDATA[Chidimma Blessing Onuora]]></dc:creator>
            <pubDate>Mon, 15 May 2023 00:04:18 GMT</pubDate>
            <atom:updated>2023-05-15T00:59:30.997Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VwiIuvexvM_5dg5i7QzRw.jpeg" /></figure><h3>Introduction</h3><p>Have you ever wondered about the intricate behind-the-scenes process that occurs when you enter a website address in your browser and hit Enter? I will be demystifying this topic as part of my tasks as an ALX student. In this blog post, we’ll take a deep dive into the journey of a simple action — typing “<a href="https://www.google.com/">https://www.google.com</a>&quot; — and explore the various stages involved, including DNS request, TCP/IP, firewall, HTTPS/SSL, load-balancer, web server, application server, and database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*6mXqMzVbRt8NQiu1zGxgPQ.png" /></figure><ol><li><strong>DNS Request:</strong> As soon as you press Enter, your browser initiates a Domain Name System (DNS) request. It contacts a DNS resolver to translate the human-readable domain name, such as “<a href="http://www.google.com/">www.google.com</a>,&quot; into its corresponding IP address. The resolver traverses the DNS hierarchy, starting from the root servers, to find the authoritative DNS server responsible for the domain.</li><li><strong>TCP/IP:</strong> Once the IP address is resolved, a Transmission Control Protocol (TCP) connection is established between your browser and the web server hosting the website. TCP ensures reliable and ordered delivery of data by breaking it into packets and reassembling them at the destination.</li><li><strong>Firewall</strong>: Before data can flow between your browser and the web server, it often passes through a firewall. The firewall acts as a protective barrier, analyzing incoming and outgoing network traffic, and enforcing security policies to prevent unauthorized access or malicious activities.</li><li><strong>HTTPS/SSL:</strong> In modern web browsing, securing data in transit is crucial. Hypertext Transfer Protocol Secure (HTTPS) encrypts the data exchanged between your browser and the web server using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols. This encryption ensures confidentiality and integrity, protecting sensitive information from eavesdropping or tampering.</li><li><strong>Load-Balancer:</strong> Popular websites like Google often employ load balancers to distribute incoming requests across multiple servers. Load balancers improve performance and reliability by efficiently allocating incoming traffic and preventing any single server from being overwhelmed. They monitor server health, distribute requests based on various algorithms, and optimize resource utilization.</li><li><strong>Web Server:</strong> After passing through the load balancer, the request reaches one of Google’s web servers. Web servers, such as Apache or Nginx, receive the request, process it, and generate an appropriate response. They handle tasks like retrieving web pages, executing server-side scripts, and interacting with other components.</li><li><strong>Application Server:</strong> For more complex web applications, an application server may come into play. Application servers, like Tomcat or Node.js, execute the server-side logic required to dynamically generate web pages or process user inputs. They provide an environment for running application-specific code and interacting with databases or other external systems.</li><li><strong>Database:</strong> Many websites, including Google, rely on databases to store and retrieve information. When you search for something, the application server communicates with a database server, such as MySQL or PostgreSQL, to retrieve the relevant data. The database server processes queries, accesses the necessary data, and sends it back to the application server for further processing.</li></ol><p><strong>Conclusion:</strong> The journey from typing “<a href="https://www.google.com/">https://www.google.com</a>&quot; in your browser to retrieving the search results involves a complex interplay of technologies and components. From the initial DNS request to the final retrieval of data from a database, each step plays a vital role in delivering the desired web experience. Understanding this process helps us appreciate the intricate infrastructure and mechanisms behind the websites we interact with daily.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=251168f53550" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>