Call to arms - SSL

Wed, 16 Aug 2017 13:30:25 +0000

For anyone who is reading this and is interested in helping out. We will slowly move towards https only at Project-GC.com. In the end we will use a redirect (301) when requesting http://project-gc.com/, and forward it to https://project-gc.com/. But first there are a few things we would like to make sure of.

Is there any part of Project-GC that does not work when using https?
Is there any place at Project-GC that links itself using http instead of https?
We would also like to always link Geocaching.com and coord.info using https (instead of http).

If you find anything that doesn't comply with the above three items, feel free to post the information here so that we can fix it.

This week we have installed new certificates for the site, since the old ones were close to expire. We have also switched to a new CDN that has better certificate handling.

Besides the fact that it's securer for everyone, this is starting to be a requirement with all the web browser restrictions. It's about time we update. But as always, time is an issue for us.

Please ignore Profile stats if the "data from" isn't at least 2017-08-17. This is due to the fact that we are caching the html for those. They might be rendered before our most recent changes.

Project-GC Q&A - Recent questions tagged ssl

Call to arms - SSL