In October 2018, Google kept its HTTP “name and shame” promise when the Chrome team flipped a switch. That switch, was to officially mark any site with an http://
scheme as insecure.
For some sites, the “nohttp” movement had begun in earnest.
But, changing the channel the browser uses is really only the first step. It’s time to clean up your build process. It’s time to clean up your documentation. It’s even time to clean up your old-school eXtensible Markup Language (XML) namespaces.