<?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 Neil Farrington on Medium]]></title>
        <description><![CDATA[Stories by Neil Farrington on Medium]]></description>
        <link>https://medium.com/@neilfarrington?source=rss-8c05e81a5fe5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tjWmoCeCkqZQSTKW.</url>
            <title>Stories by Neil Farrington on Medium</title>
            <link>https://medium.com/@neilfarrington?source=rss-8c05e81a5fe5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:25:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@neilfarrington/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[Captive Portals and HTTPS]]></title>
            <link>https://medium.com/@neilfarrington/captive-portals-and-https-3d6d2bf6c81c?source=rss-8c05e81a5fe5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d6d2bf6c81c</guid>
            <category><![CDATA[https]]></category>
            <category><![CDATA[captive-portal]]></category>
            <category><![CDATA[wifi]]></category>
            <dc:creator><![CDATA[Neil Farrington]]></dc:creator>
            <pubDate>Mon, 23 Apr 2018 07:31:44 GMT</pubDate>
            <atom:updated>2018-04-23T07:33:21.185Z</atom:updated>
            <content:encoded><![CDATA[<p>When connecting to a public WiFi network, the network will often rely on waiting for a user to attempt to visit a website, and then redirect them to a captive portal to register or activate their connection.</p><p>If you’re anything like me, when you connect to public WiFi you know you’re going to be redirected, and so you visit a common domain such as <a href="https://google.com/">google.com</a> or <a href="https://www.bbc.co.uk/">bbc.co.uk</a>. However, I also have HTTPS Everywhere installed, which means my browser automatically upgrades these sites to HTTPS, and I’m <a href="https://www.eff.org/https-everywhere/faq#why-is-https-everywhere-preventing-me-from-joining-this-hotelschoolother-wireless-network">prevented from joining the network</a>. So instead, I visit one of the websites I host and run, except they’re all HSTS-enabled and preloaded, which causes <a href="https://www.wirelessphreak.com/2017/05/captive-portal-and-hsts-issues.html">the same problem</a>. With more websites becoming HSTS-enabled, I tend to find less and less websites I can use for captive portal redirects.</p><p>To complicate matters, I’ve also probably gone through these steps before I remember I have custom DNS servers set, which I may need to remove in order for the redirect to work in any form.</p><p>At this point, exasperated, I tend to open up Terminal and run <em>curl -v google.com</em> to find out where it’s redirecting me to, and copy this into the browser. I could just type a fake URL in the address bar, but if I <em>am</em> connected to the internet, I’ll receive an error which could be misleading or, knowing my luck, it’ll be a real site with objectionable content or a nasty virus ready and waiting.</p><p>Since it would be much easier to have a website I know will always work and is easy to remember, which can sit in my browser history so it’s also easy to navigate to, <a href="http://httponly.site/">HTTP Only</a> was born. By not serving content over HTTPS, and not enabling HSTS, <em>HTTP Only</em> provides an easy way to connect to public WiFi networks with captive portals. I can simply visit <a href="http://httponly.site/">http://httponly.site</a> after connecting to a public WiFi network to be redirected. And if the <em>HTTP Only</em> site loads successfully, then I know I’m connected.</p><h4>Avoiding the Problem Entirely</h4><p>Luckily, there are a number of systems in place that mean not <em>all</em> public WiFi networks cause this problem.</p><p>At an operating system level, there are systems such as Apple’s Captive Network Assistant to help the user connect to the network.</p><p>At a browser level, modern browsers such as Google Chrome have <a href="https://www.chromium.org/chromium-os/chromiumos-design-docs/network-portal-detection">network portal detection built in</a>.</p><p>There is also an IETF working group for <a href="https://datatracker.ietf.org/wg/capport/about/">Captive Portal Interaction (CAPPORT)</a>, which will help solve this problem at a higher level.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d6d2bf6c81c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>