As most people will be aware, as time goes on, security on the internet becomes more and more of an issue. To help keep web users safe, various organisations are encouraging site owners to switch from unencrypted content, to SSL secured content (denoted by https at the start of the web address). For a long time now, any site taking credit cards would use SSL to ensure sensitive card information couldn't be accessed by unauthorised persons. By switching to SSL throughout, all information, including usernames and passwords gains an increased level of protection against malicious attacks. This increase in protection is particularly beneficial if you access the internet over a 3rd party or public wifi connection, which pose a particular risk from "man in the middle" attacks from other users on the same network.
In order to keep up with these changes, we've now implemented SSL support on the forum. The site can still be accessed as before, using the non-SSL address http://www.genealogyforum.co.uk, or using SSL with increased security, via https://www.genealogyforum.co.uk
If you're accessing the site from a public network, we'd recommend using the new https URL, so all data transferred between your browser and our server is encrypted. If you're using a trusted home or work network, you can optionally continue to use the old http URL, or switch to the new one at your own discretion. When using the new URL, you should see a padlock in the browser address bar verifying the increased security level.
If you choose to use the new secure URL, some content which doesn't offer the same level of security may be blocked - so you may find the odd missing attachment, or embedded image missing.
When accessing via the new SSL URL, previous cookies can no longer be accessed, which may cause access issues. Before accessing the new URL, we'd recommend logging out of the forum, then clicking the "Delete all board cookies" link at the bottom right hand corner of any forum page.
SSL support should work with most current devices, but may be problematic with very old PCs and some older mobile phones or tablets. If this proves to be the case, the old non-SSL URL will continue to work for the time being, however, it's likely that at some point in the near future, security warnings in web browsers may force us to point all requests at SSL pages.
Hopefully I've managed to communicate all of that clearly! Any queries or concerns, please let me know.