<?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 Gwendal Minguy-Pèlerin on Medium]]></title>
        <description><![CDATA[Stories by Gwendal Minguy-Pèlerin on Medium]]></description>
        <link>https://medium.com/@gwendalminguy?source=rss-fa1d9a3c4e3d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8NH3-4ejJIduDmxH5GwW-A.jpeg</url>
            <title>Stories by Gwendal Minguy-Pèlerin on Medium</title>
            <link>https://medium.com/@gwendalminguy?source=rss-fa1d9a3c4e3d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:48:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gwendalminguy/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 a web address into your browser and press enter?]]></title>
            <link>https://medium.com/@gwendalminguy/what-happens-when-you-type-a-web-address-into-your-browser-and-press-enter-aaf1cd5c37af?source=rss-fa1d9a3c4e3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaf1cd5c37af</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Gwendal Minguy-Pèlerin]]></dc:creator>
            <pubDate>Sat, 27 Sep 2025 16:30:21 GMT</pubDate>
            <atom:updated>2025-09-27T16:30:21.971Z</atom:updated>
            <content:encoded><![CDATA[<p>When you type a web address into your browser and press enter, a surprising number of steps happen behind the scenes before the page appears. The domain name must be translated into an IP address, a secure connection has to be established, firewalls and load balancers process the traffic, and finally the web, application, and database servers work together to generate the response. To make this process clearer, we can break it down into smaller sections, each explaining one stage of the journey.</p><h4><strong>DNS Resolution</strong></h4><p>When a user tries to access a website such as <em>https://www.google.com</em> from their browser, the <strong>Domain Name</strong> must first be translated into an <strong>IP Address</strong> to establish the connection. To find this address, the browser will first check its own <em>cache</em>, where the entry may exist if the website has been visited recently. If not, it will ask the operating system, which will also check its <em>cache</em>, and then the <em>hosts</em> file. If the IP address is still not found, the operating system will contact the configured <strong>DNS Server</strong>, which acts like a directory for the internet. It translates human-readable names (<em>google.com</em>) into numerical IP addresses (<em>8.8.8.8</em>). The IP address is then sent back to the operating system and passed on to the browser.</p><h4><strong>TCP Connection</strong></h4><p>Now that it knows the correct IP, the browser opens a connection to the server using the <strong>Transmission Control Protocol</strong> (TCP). When data is sent over the internet, it is broken down into small chunks called packets. The TCP connection establishes a <strong>reliable channel</strong> by ensuring that both the client and the server agree on how these packets will be numbered and acknowledged, so they can be reassembled in the right order. This guarantees that the full message arrives correctly, even if packets take different routes across the network.</p><h4><strong>HTTPS &amp; TLS Certificate</strong></h4><p>Once the connection is established, there is another step before the browser actually asks for the desired page, since the <strong>Hypertext Transfer Protocol Secure</strong> (HTTPS) is being used. The secure version of HTTP means all traffic must be encrypted. To achieve this, the browser signals to the server that it wants to use the <strong>Transport Layer Security</strong> (TLS) protocol and requests a <strong>TLS Certificate</strong>. This certificate is used so that the browser and the server can securely exchange keys, enabling encryption of all future communication.</p><h4><strong>Firewall</strong></h4><p>Most servers today have a <strong>Firewall</strong> set up for security purposes. It helps filter unwanted connections and strengthens network security by allowing or blocking attempts based on several criteria:</p><ul><li><strong>Port Blocking</strong>: A classic firewall can be configured to restrict available ports for external connections, such as allowing only port <em>443</em> to enforce the use of <em>HTTPS</em>. If a client tries to connect to any other port, the connection will be dropped. This ensures that only the intended services are reachable.</li><li><strong>Traffic Filtering</strong>: A firewall can block certain <strong>types of traffic</strong>, such as <em>P2P</em>, or restrict access to a <strong>specific IP range</strong> by denying connections from outside that range. This can also be used to implement <strong>geolocation rules</strong> to deny connections from specific countries or regions.</li><li><strong>Port Scanning</strong>: A firewall can block probes that attempt to scan for open ports in search of weak entry points. This prevents malicious actors from trying to break into the server.</li><li><strong>Common Attacks</strong>: A <strong>Web Application Firewall</strong> (WAF), placed where traffic is already unencrypted, can filter malicious payloads to prevent <strong>SQL or XSS injections</strong>, or detect and drop abnormal surges of traffic to mitigate <strong>Denial-of-Service</strong> (DoS) attacks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVa8El66rA8zzsuE1GMyUw.png" /><figcaption>What happens when you type google.com in your browser and press enter?</figcaption></figure><h4><strong>Load-Balancer</strong></h4><p>In the case of a <strong>Distributed Web Infrastructure</strong>, where the web stack (such as the combination of a <strong>Web Server</strong>, an <strong>Application Server</strong>, and a <strong>Database Server</strong>) is replicated across several instances to handle high traffic, the request first arrives at a <strong>Load Balancer</strong> before being treated. This is a software or hardware component that uses a <strong>distribution algorithm</strong> to spread requests across multiple servers. The <strong>round robin</strong> algorithm is a common and simple approach, forwarding requests sequentially to each server in turn. By distributing the load, heavy traffic can be handled efficiently, reducing performance issues and ensuring a smoother user experience.</p><h4><strong>Web Server</strong></h4><p>When the request reaches one of the servers, the first component it encounters is the <strong>Web Server</strong> (commonly software like <em>Nginx</em> or <em>Apache</em>). The web server’s role is to handle incoming HTTP requests and decide what to do with them. If the request is for a <strong>static resource</strong> (such as an image, a CSS file, or a JavaScript file), the web server can serve it directly from its file system without needing to ask anything else. If the request concerns a <strong>dynamic resource</strong>, such as a page that depends on user data or account information, the web server forwards the request to the <strong>Application Server</strong> for further processing.</p><h4><strong>Application Server</strong></h4><p>The <strong>Application Server</strong> is responsible for running the actual <strong>business logic</strong> of the website or application. It takes the request forwarded by the web server and interprets it according to the application code (written in languages like <em>Python</em>, <em>Java</em>, <em>PHP</em>, or <em>Node.js</em>). For example, if the user requested their profile page, the application server determines what data is needed, applies any required rules or checks (like verifying that the user is authenticated), and prepares the necessary instructions to fetch data from the <strong>Database Server</strong>. It then combines that data with templates or logic defined in the application code to generate a dynamic response, usually in the form of an HTML page.</p><h4><strong>Database Server</strong></h4><p>The <strong>Database Server</strong> is where the persistent data of the application is stored and managed (using systems like <em>MySQL</em>, <em>PostgreSQL</em>, or <em>MongoDB</em>). When the application server sends a query (such as getting all information for a specific user), the database server processes it by searching its stored tables or documents and returns the matching results. The application server then takes this raw data, structures it according to the application’s needs, and sends it back to the web server. Finally, the web server packages this response into an HTTP reply that travels back over the network to the user’s browser, where the requested page is displayed. In a <strong>Distributed Web Infrastructure</strong>, where several instances of the application exist to handle heavy traffic, the <strong>Database Server</strong> also needs special consideration. If every server had its own isolated database, the data could quickly become inconsistent. To solve this, most systems rely on a <strong>Primary-Replica model</strong>. In this setup, a single <strong>Primary Database</strong> handles all write operations (such as <em>inserting</em> or <em>updating</em> user information), and these changes are then replicated to one or more <strong>Replica Databases</strong>, which can be used for read operations. This ensures that data stays synchronized across the infrastructure: users can connect to different servers without seeing outdated or conflicting information, while the workload is distributed between multiple database instances.</p><p>In the end, what seems like a simple action — typing a web address and pressing enter — is actually the result of many layers of technology working together seamlessly. From networking protocols and encryption to security filters and distributed server infrastructures, each component ensures that the right data is delivered quickly and securely to the user’s screen. This hidden complexity is what allows the modern web to feel simple, fast, and reliable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaf1cd5c37af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>