Ian
Administrator
- Joined
- Jul 26, 2011
- Messages
- 1,040
- Reaction score
- 1,169
- Hardiness Zone
- 9a
- Country
About a week ago, we moved GPF from an http site to one that uses https - which basically means that it uses a secure, encrypted connection. Google and other big internet companies are pushing hard for this, so nearly all sites will use the same encryption that you see when buying online at places like Amazon.
As part of this move, we have to make sure that everything on the page comes from a secure website, otherwise the browser will report that the entire page is insecure. So, the forum software does something clever and "caches" images so that they load from the GPF https webite, even though they are hosted elsewhere - it's the only way to get a secure site.
The downside of this caching is that it only updates once per week, so any dynamic weather sig images won't update instantly. I'm not aware of a way around this, but I know that many members really appreciate having this image in their sig, so I want to find a way to make it work.
We can't go back to http, as Google Chrome is going to start listing sites that have login forms as "insecure" if they don't make the switch. Over the next month or two, many other sites are going to have to make the jump.
I wanted to post this message as Becky had a PM from a member that had found this problem, so I'm looking in to what I can do right now .
As part of this move, we have to make sure that everything on the page comes from a secure website, otherwise the browser will report that the entire page is insecure. So, the forum software does something clever and "caches" images so that they load from the GPF https webite, even though they are hosted elsewhere - it's the only way to get a secure site.
The downside of this caching is that it only updates once per week, so any dynamic weather sig images won't update instantly. I'm not aware of a way around this, but I know that many members really appreciate having this image in their sig, so I want to find a way to make it work.
We can't go back to http, as Google Chrome is going to start listing sites that have login forms as "insecure" if they don't make the switch. Over the next month or two, many other sites are going to have to make the jump.
I wanted to post this message as Becky had a PM from a member that had found this problem, so I'm looking in to what I can do right now .