Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Sylvia Else <sylvia@email.invalid>
Newsgroups: comp.misc
Subject: How is public WiFi meant to work?
Date: Sat, 20 Apr 2019 12:50:10 +1000
Lines: 19
Message-ID: <ghvfn4FochgU1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net HpO1qD1o1N6Sq0dthiUTCA9FW3V2uydHIjrvxUXDs4bGEXzy2M
Cancel-Lock: sha1:8jfTGkFREtTse6/YlNhPPY61oBw=
X-Mozilla-News-Host: news://news.individual.net:119
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
Content-Language: en-GB
Xref: csiph.com comp.misc:17854

In the days of yore, one chose a public WiFi node, and then when one 
entered a URL into a browser, the WiFi node served up a page that 
redirected one to a terms-acceptance page. One clicked on that. Job done.

These days, the URL one enters is likely to be for the https protocol. 
The WiFi node cannot redirect that, and nor can it pretend to be the 
target page.

So, in today's world, just how is this meant to work?

I seem to have no end of trouble with it, at times resorting to entering 
the URL of a page of my own that is not https based.

Sylvia.