This should reduce the chances of the site being blocked by firewalls.

It should also fix the problem where upcoming and future versions of Google Chrome will be warning about and/or blocking any non-SSL web sites.

As somebody whose knowledge of website creation stops with basic HTML, who isn't even versed with style sheets, and who only found out that [bgsound] wasn't supported by modern browsers a week ago, I'm horrified that I might have to do more things to keep my website available to these new-fangled browsers.

So, if you don't mind me asking, what do I need to do?

And while I'm on plaintive technical enquiries, have you any idea why the page of Al. B's recent post is showing up when I archive it like this? I'm baffled.

Start by seeing if your web host supports SSL already. Second, see if the web host will use Let's Encrypt SSL certificates (those are free) or if you have to use a paid one. If they can't or won't do it, consider a new host in the next year or so.





It looks like the Stylesheet is missing. Change the http: in the LINK lines at the top to https: instead.

After some reflection, I'm not sure it would be worth the time and trouble to shift my site to ssl compliance. It's only a collection of pages for people to look at, with no interactivity at all. There's no merchant pages, no forms, no surveys, no advertising, not even hit counters. So I'll probably leave well alone for now.

Quote:



Quote:
And while I'm on plaintive technical enquiries, have you any idea why the page of Al. B's recent post is showing up when I archive it like this? I'm baffled.

Quote:
It looks like the Stylesheet is missing. Change the http: in the LINK lines at the top to https: instead.

I'll take a pass at that when I'm feeling technical. But why that one page amongst so many others that work okay?

It's not a hurry yet, I have a lot of people reading the sites on this server (besides this one) so I had to stay ahead of the game. Comicboards.com still isn't caught up yet, for instance.





Caching maybe? Eventually all the URL's at parodyverse.strike-two.com will redirect from http to https.

After some experimentation the https update seems to be the glitch. When I save a https page from the site and load it in my archive that preserved page isn't calling up the page background or some style sheet material, which results in a default white background and, for some reason, centralised text throughout.

I suspect this is a feature of the ssl callup objecting to being hauled to a different url but I don't know enough about it to diagnose properly.

The workaround seems to be to delete the s after the http and save the resultant non-https version, which archives just fine.

I noticed some issues with it too, so I turned off the auto-redirect to https and make it optional instead. So both kinds of links should work.