On Wed, Apr 14, 2021, 11:57 PM Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote:
> Kenneth Parker <sea7k...@gmail.com> writes: > > > On Wed, Apr 14, 2021 at 10:16 PM Celejar <cele...@gmail.com> wrote: > > > > On Wed, 14 Apr 2021 22:57:01 +0100 > > piorunz <pior...@gmx.com> wrote: > > > > > On 14/04/2021 17:19, Celejar wrote: > > > > Hi, > > > > > > > > I recently switched to Firefox's native HTTPS-Only mode from the > > > > HTTPS Everywhere extension, and I've just made the nasty discovery > that > > > > a bunch of links that had been returning 404, which I had been > assuming > > > > were dead links, were actually perfectly valid pages, which Firefox > had > > > > been "upgrading" to HTTPS, and then getting 404s from web servers > that > > > > weren't offering them via HTTPS (but still apparently accepting > > > > connections via HTTPS). Clicking on the little lock icon and turning > > > > HTTPS-Only mode off for the website doesn't seem to have any effect > - > > > > the only thing that lets me actually access these pages is turning > off > > > > HTTPS-Only mode via the general Settings page (or about:config). > > > > > > > > When the website doesn't offer HTTPS at all, then Firefox offers to > > > > connect via HTTP, after a warning, and that's fine. But having pages > > > > become completely inaccessible is intolerable - I now have to check > > > > every 404 I get by turning off HTTPS-Only mode and seeing if the > > > > page is actually there. Am I missing something here, or is > HTTPS-Only > > > > mode just badly broken? > > > > > > It certainly works fine for me. I use https only mode for many months > > > now. Can you bring an example of a page which returns good page on > http, > > > but 404 error on https? > > > > http://www.daat.ac.il/ > > https://www.daat.ac.il/ > > > > Celejar > > > > Indeed: A "Universe Site" that I host on Linode doesn't use https. So, > > https://eyeblinkuniverse.com -- doesn't work: "Problem loading > page - Unable to connect" > > http://eyeblinkuniverse.com -- Works properly on my version of > Firefox: Firefox 78.9.0esr (64-bit) on Debian Bullseye. > > > > Does this mean that I can look forward to this failure, when the new > Firefox comes out? Why can't people still make simple, text-based web > > pages that can be read to a Blind Person? See, I don't do forms, data > entry, or anything on my opening screens. For that, it links to a > > Blogspot, which uses some of Google's Bells and Whistles. > > > > In other words, is this the end of the "Simple Web"? > > https has nothing to do with "simple web" -- I term I don't remember > having seen before, but I like. All the TLS negotiation is handled by > the web server and browser, and it's easy enough to set up with > letsencryupt that there's really no excuse for not doing it (says the > guy who hasn't gotten it set up yet for a shotgun club web site he > manages... really need to do that...). > I use lighttpd for eyeblinkuniverse.com, with nano as my editor. I don't quite understand the Certificates required for https. I guess it is time for some lessons. Thanks! Kenneth Parker >
