<?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 Patrick Orangi on Medium]]></title>
        <description><![CDATA[Stories by Patrick Orangi on Medium]]></description>
        <link>https://medium.com/@patrickorangi?source=rss-4cff8b8aaf8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dr4N99XSb_zsya9rx2p4GQ.jpeg</url>
            <title>Stories by Patrick Orangi on Medium</title>
            <link>https://medium.com/@patrickorangi?source=rss-4cff8b8aaf8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:52:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@patrickorangi/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[The Secret Meeting your browser doesn’t tell you about.]]></title>
            <link>https://patrickorangi.medium.com/the-secret-meeting-your-browser-doesnt-tell-you-about-dcb30e32f9b8?source=rss-4cff8b8aaf8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcb30e32f9b8</guid>
            <category><![CDATA[firewall]]></category>
            <category><![CDATA[http-request]]></category>
            <category><![CDATA[https]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[dns]]></category>
            <dc:creator><![CDATA[Patrick Orangi]]></dc:creator>
            <pubDate>Mon, 06 Sep 2021 09:35:05 GMT</pubDate>
            <atom:updated>2021-09-06T10:34:10.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KqAQu4Dy8cwELZCA" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>How sinister, you think. Could my browser be plotting my downfall? After all, it knows way too much about me! The simple thought of it throws you into a wild frenzy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*To_GIIQ2wQtpujeO" /><figcaption>Photo by <a href="https://unsplash.com/@viniciusamano?utm_source=medium&amp;utm_medium=referral">Vinicius &quot;amnx&quot; Amano</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You immediately summon your browser to bring to light what that “secret” meeting is all about. The reply is pure soap opera parlance; <em>“I did it to protect you” or “It’s because I love you” or “It’s for the greater good”</em>. The feeling in your gut doesn’t help that you’re having none of it. Well, grab a chair(<em>or a browser..hahaha</em>) and let me tell you all about what happens when you type in <a href="http://www.holbertonschool.com/"><em>www.holbertonschool.com</em></a> in that nifty search bar and press Enter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nHylTd9wjy7-lE9uTi0XlQ.png" /><figcaption>Parts of a URL. Copyright: MDN.</figcaption></figure><p>First and foremost, it involves a whole board meeting choke full of acknowledgements, handshakes, certificates etc. This only worsens your suspicions and at this point you’ve had enough. <em>“It’s time for war”</em>, you tell yourself.</p><p>The whole process is akin to a board meeting(<em>without the bureaucracy</em>) that makes decisions on the fly so effectively that you don’t even notice they are there. Without further ado, let me introduce you to the said board members:</p><p><strong>DNS — Domain Name Server</strong></p><p>Typically, servers don’t actually know the website/page you’re requesting by its name, only by it’s <strong>IP address</strong>. Parts of a <strong>URL</strong> (www.holbertonschool in our case) are shown in the graphic above. A <strong>DNS</strong> resolves/translates the given <strong>URL</strong>( <em>Uniform Resource Locator</em>) into the relevant IP address to enable the browser to serve the requested webpage. <em>The “board” is quite simply your web butler service</em>. Domain Name Resolution first starts by doing a lookup in the browser’s DNS cache then to your Internet Service Provider cache and so on.</p><p><strong>TCP/IP — Transmission Control Protocol/Internet Protocol</strong></p><p>This is quite simply a set of rules for how information is transmitted between computers over a network. TCP/IP can be likened to the traffic rules followed when driving from point A to B. You can find more on this at <a href="https://www.ibm.com/docs/en/aix/7.1?topic=protocol-tcpip-protocols">TCP/IP Layers and flow of information.</a></p><p><strong>Firewall</strong></p><p>A firewall is your <em>knight in shining armor</em> i.e. network security system that monitors your network’s incoming traffic to ensure all preset rules are met and also to prevent malicious attackers/software from gaining access to your system. Firewalls operate on different layers of the <strong>OSI Model</strong>( <em>Open Systems Interconnection</em>) depending on their type, functionality and security needs of the system on which they have been installed. <a href="https://www.geeksforgeeks.org/layers-of-osi-model/">OSI Model</a> is comprised of 7 layers, each with its own functionality, that work collaboratively to transmit data between two users/nodes globally. More on <a href="https://www.orbit-computer-solutions.com/firewall-explained/">firewall functionality on the different OSI layers.</a></p><p><strong>HTTPS/SSL</strong></p><p>HTTPS is an acronym from <strong><em>HyperText Transfer Protocol Secure</em></strong> while SSL is an acronym for <strong><em>Secure Sockets Layer</em></strong>. HTTPS basic function is to ensure secure communication over a computer network achieved through encryption by SSL. HTTPS over SSL authenticates the accessed website and enforces privacy and integrity of data while in transit. This protects the users from eavesdroppers and man-in-the-middle attacks which would otherwise allows hackers to snoop on your data. The browser achieves this by using digitally-signed certificates which are then checked against Certificate Authorities (provide valid certificates) in-built into the browser.</p><p><strong>Load-balancer — yeah, it’s aptly named.</strong></p><p>A load balancer is essentially a “traffic cop” of sorts that routes incoming traffic efficiently which helps to optimize site performance and reliability by reducing downtime, maximizing speed and provides flexibility to add or subtract servers as demand dictates which reduces the cost of running a website. Load balancers also reduce downtime by only sending requests to servers that are online. Load balancing is thus the last word in redudndancy. Load balancers can be either hardware or software based with the latter being more common. Software load balancers employ the most relevant algorithms for the required performance needs. Some load balancing algorithms include; <strong>Round Robin</strong> <em>which distributes requests among a group of servers sequentially, </em><strong>Least Time</strong><em> which sends requests to a server by considering fastest response time and fewest active connections. </em>Others include<em> </em><strong><em>least connections, hash, IP hash</em></strong><em> among several others.</em></p><p><strong>Web Server</strong></p><p>Web Servers are quintessentially the ‘<em>waiters</em>’ of a server in that they receive your order(<em> </em><strong><em>request from your browser in our case</em></strong>), fetch your order(<strong><em>by means of a HTTP request</em></strong>) then finally serve it to you(<strong><em>through HTTP</em></strong>) or return a useful error message if the resource is unavailable. Most common error is: <strong><em>404 NOT FOUND</em></strong>. Therefore a web server is software that enables real/virtual servers to carry out specific tasks over a given protocol e.g <strong>HTTP </strong>for serving web pages<strong>, SMTP(</strong><em>Simple Mail Transfer Protocol</em><strong>) </strong>used for email<strong> </strong>and<strong> FTP</strong>(<em>File Transfer Protocol</em>) for file transfer and storage. Gmail, Outlook and any other email service use SMTP. Cloud storage services like Dropbox, Google Drive, iCloud etc achieve their capabilities through FTP. You finally know how that <em>‘I hope this email finds you well</em>’ lands in your inbox. Web Servers can be categorized on the type of content they serve which is either; <strong>Static content</strong>(<em>web pages</em>) or <strong>Dynamic content</strong>(<em>web apps e.g Twitter for Web or accessing and updating databases</em>) Commonly used web server Software include; Apache HTTP Server, Nginx, Microsoft Internet Information Services etc.</p><p><strong>Application Server</strong></p><p>An application server is quite similar to a web server in its functionality only that it’s exclusive to delivering dynamic content i.e “Business Logic”. They are servers designed to install, operate and host applications. It’s akin to going to your local mechanic and asking them to change your oil, he/she essentially gives you access to carry out the functionality of carrying out the oil change. Web and application servers typically work hand in hand since websites usually provide static and dynamically generated content. A good example is NGINX Plus. You want to watch some Netflix? Better talk nice to your Application Server.</p><p><strong>Database.</strong></p><p>A database is simply where information is stored within our web stack. It’s the cookie jar without which, life in the information age that we live in today won’t make any sense. Databases are at the very back end of our web infrastructure design, they’re essentially who &amp; what the system is and does. Instagram is typically a picture database if you remove all the obscurity of likes and follows( all those metrics are also stored in the database.. gotcha!)</p><p>The figure below illustrates a simple web stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*XrRnp7wEYjfcVVDh.jpg" /><figcaption>Source: Google Images.</figcaption></figure><p>In retrospect, that secret meeting isn’t so bad after all, when it works flawlessly.</p><h3>Conclusion</h3><p>When you press ENTER, the DNS resolves the URL into an IP after which the browser sends a HTTP request to the relevant web server while adhering to TCP/IP as the mighty HTTPS/SSL stands guard. The web/application server, being at your service, consequently fulfills your requests by sending another HTTP response whose header gets validated by both HTTPS/SSL and the firewall after which the webpage or application request if then fetched over HTTP and voila.. your webpage is finally in your desktop.</p><p>You’re now a Web Houdini, get out there and do some magic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcb30e32f9b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>