HTTPS / SSL Thanks to Rootsweb for starting to include SSL encryption on our web sites. Several things still need to be included to complete the full installation of SSL encryption. First is to automatically switch URL entries such as http://sites.rootsweb.com/~websiteid<http://sites.rootsweb.com/%7Ewebsiteid>, sites.rootsweb.com/~websiteid, to https://sites.rootsweb.com/~websiteid<https://sites.rootsweb.com/%7Ewebsiteid> when entered as a URL in the web browser. For now unless you enter the https:// when you enter the URL to view your website the web browsers are showing the websites as UNSECURE. Next I noticed that the https:// is NOT being carried forward to sub-directories. Each of my different family pages are in a sub-directory under my main ~websiteid directory therefore these sub-directories are being shown as UNSECUREs. I’m sure both of these are possible as I manage several other web sites on different hosting services and they both work as suggested above. Still not able to access my military web site under military_html sub-directory but the last I remember was that this would come later. Again I do appreciate Rootsweb getting my genealogy web site back on line. Other then the SSL encryption items above my ~wlsetzer web site is back on line and updated. Wayne https://sites.rootsweb.com/~wlsetzer/<https://sites.rootsweb.com/%7Ewlsetzer/>

Wayne wrote: First is to automatically switch URL entries such as http://sites.rootsweb.com/~websiteid<http://sites.rootsweb.com/%7Ewebsiteid <http://sites.rootsweb.com/~websiteid>>,sites.rootsweb.com/~websiteid, to https://sites.rootsweb.com/~websiteid<https://sites. rootsweb.com/%7Ewebsiteid <https://sites.rootsweb.com/~websiteid>> when entered as a URL in the web browser. For now unless you enter the https:// when you enter the URL to view your website the web browsers are showing the websites as UNSECURE. --- Google Chrome has started labeling ALL mixed content websites as unsecure as a new push for all sites to switch to https. Mixed Content means a combination of http and https. From research I did on this last month, it is not as horrid as they are making it sound. It is not truly unsafe. It only means our sites have http pages, while the host has made top level into https (e.g. www.rootsweb.com).