https Links without www Prefix
Sometimes, when the www prefix to highlandwoodworking.mom is omitted, following a link generates a certificate (privacy) error. I suspect this is a flaw in the NS certificate, which covers www.highlandwoodworking.mom but not highlandwoodworking.mom.
The blog does not have this problem. The domain names blog.woodworkingtooltips.com, www.woodworkingtooltips.com, and woodworkingtooltips.com are covered by the blog's certificate. You can access the blog using https:// prefixed to any of these domain names.
Some Guidelines
Here are some guidelines for safely coding a link to a highlandwoodworking.mom page or image:
You don't have to code the https/http protocol--consider the "inherited" protocol syntax below.
From within a (www.)highlandwoodworking.mom page, you don't have to code the host name but, if you do, use the www prefix.
Don't use explicit http for highlandwoodworking.mom or www.highlandwoodworking.mom URLs. For an image reference, you'll get "mixed content error". For a page link, it will work by quirk (see below) but is a bad idea. Use either inherited protocol or explicit https protocol.
Links for Testing and Demonstration
https://highlandwoodworking.mom/workbenchsale.html. Static page link with explicit https and no www prefix. This generates a certificate error. If you replace the https with http and the page has the static-html-cleanup.js javascript, the link works (because the javascript changes to https and adds the www prefix). The cleanest correction for this link is simply /workbenchsale.html (or you could add the www prefix to the original URL).
//highlandwoodworking.mom/workbenchsale.html. Static page link with inherited http/https protocol and no www prefix. This link will always fail because this enclosing aspx page is always forced to https, which gets inherited, producing the equivalent of item #1 above. The correction is similar to the correction for item #1.
https://highlandwoodworking.mom/about-us.aspx. aspx page link with explicit https and no www prefix. Change the https to http and it works (because, for an aspx reference, NS converts http to https and inserts the www--this is a quirk). But the safe correction is similar to the correction for item #1.
//highlandwoodworking.mom/about-us.aspx. aspx page link with inherited http/https protocol and no www prefix. This link will always fail because aspx pages are always forced to https, which gets inherited, producing the equivalent of item #3 above. The correction is similar to the correction for item #1.
aspx Pages versus Static Html Pages
There are two types of pages at (www.)highlandwoodworking.mom: aspx and (static) html. The https/http handling is different for each type:
aspx pages always load as https, even if the NS server has to do a redirection from http to https.
Static html pages will load via http; if the static page includes the static-html-cleanup.js javascript, that javascript will redirect from http to https. We do this redirection to give the user confidence wrt privacy.
Using Inherited Protocol
A note on using "inherited" protocol, i.e., the "//www.highlandwoodworking.mom..." form: If you have an html snippet in a file and you want to test without being enclosed in an aspx page, using inherited protocol for links might be undesirable. If you load an html file into a browser, the protocol is "file://" and links that inherit the file protocol will not work.
Coding the links as "https://www.highlandwoodworking.mom..." allows the html to be tested "stand-alone" with the file protocol. The variation table html files now use this form and those files can now be tested directly in a browser.