Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Sylvia Else Newsgroups: comp.misc Subject: Re: How is public WiFi meant to work? Date: Sat, 20 Apr 2019 16:54:36 +1000 Lines: 46 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net PwTRxEep4fMGat/KUqBM+ASv1Hw+IlahcwWmVq6sqw6Sj46VrH Cancel-Lock: sha1:YqdVVEvmnflujGyL6x0kuS2JBa8= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 In-Reply-To: Content-Language: en-GB Xref: csiph.com comp.misc:17857 On 20/04/2019 3:02 pm, Rich wrote: > Sylvia Else wrote: >> 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. > > That is the solution, well, a http page, not necessarially your own, > but at least when you own it you know it will not suddenly switch to > https out of the blue. > > Android phones work around this glitch by querying a set of google > http: servers that presumably google specifically setup for keeping > these captive portal pages working (and, of course, giving Google even > more metadata with which to market things to you). > What a kludge! Well, that's a pain. I'm trying to assist an aged person with zero IT smarts (or let that be negative, if it's meaningful). I was hoping there was a solution that I could just implement. Even bookmarking a suitable URL in Chrome may be asking too much. A quick ap search (there's an ap for everything, right?) didn't reveal anything useful. On the face of it, any site should do, as long as its domain name exists, since one isn't going to reach it until after the WiFi node has done its thing. Except for Google, since searches sometimes seem to be allowed through. I think I've found a way to put something on the home screen that starts Chrome and makes it go to the chosen URL. Took some doing - Chrome seems to have ideas of its own about when it's going to let one do that. I think they must have already incorporated my confiseauser.jar library. Where are my licence fees? Sylvia.