Just a little bit over a year ago, I wrote about the Internet Archive’s Smart 404 Handler, which aimed to help site owners put an end to useless 404 Not Found errors on their own site by offering a link to the content (if available) on the Wayback Machine. Now, the Internet Archive has set out to solve the problem of useless 404 Not Found errors for everyone with a new extension for Firefox, for Chrome, and for Safari!
With the extension installed, if you encounter a 404 (or really any from the range of “unavailable” errors) for content that exists in the archive, you’ll see this very handy pop-up:
As that button describes, clicking it will take you to the archived page, so you’ll never have to wonder about what you were missing. But, that’s not all! Do you feel like a page looks a little bit different today? Are you feeling nostalgic for how pages looked when they were first published? Just open the extension in your browser’s toolbar for even more fun:
Thanks to this new extension, and the Wayback Machine’s hundreds of billions of archived pages, the experience of missing out on lost content could finally be a thing of the past! Also, if you find this extension useful, don’t forget that the Internet Archive needs donations to be able to provide all of that for free.
For as far back as I can remember, browsers have always denoted HTTPS pages with a padlock icon, a tiny warning to let you know that anything you submit on the specific page will be securely encrypted. As with all never-changing warnings though, I imagine you’ve stopped noticing it as much as you used to years ago, and that effect combined with HTTPS usage reaching over half of all web pages and the popularity of extensions like HTTPS Everywhere, has spurred some changes in how Firefox and Chrome approach this.
Launched this week, Firefox 51 and Chrome 56 have reversed that age-old warning. Login forms over HTTP now display a “Not Secure” warning. This new warning should be enough to catch the attention of those of us who have begun to ignore the time-honored padlock, but I imagine site owners might be caught a bit off guard.
If you own a site with a login form over HTTP, don’t worry (sort of), your login form isn’t suddenly not secure … it has never been secure. If you’re the only person who uses that login form, and you never use it over a public internet connection, you generally have nothing to worry about.
If other people are expected to log in to your site over HTTP, or you often log in over a public internet connection, it’s time to start moving your site over to HTTPS. You’ll need to acquire an SSL/TLS certificate from a certificate authority to being with, and in the past those have been ridiculously expensive, but all of that changed when Let’s Encrypt premiered, offering free SSL/TLS certificates for everyone. Today, you’ll most likely find that your hosting provider either offers free or incredibly inexpensive certificates, like all of WordPress’s recommended hosting providers do. If your hosting provider still wants to charge you a ridiculous rate for a certificate, you might as well take this opportunity to check out the rapidly growing list of hosting providers who offer free Let’s Encrypt certificates.
Once you have your certificate, setting it up is generally just a matter of consulting the documentation from your hosting provider (though this is typically automated if you acquire the certificate from them) and your website’s software. If you use WordPress, the process is very simple.
As site owners, let’s do what we can to proliferate HTTPS and thus provide a more safe and secure web for everyone.