Moderators: richierich, ua900, PanAm_DC10, hOMSaR
chunhimlai wrote:When will this website be upgraded to https?
Cush wrote:I don't understand why Airliners.net has not yet implemented their SSL? With all of the major changes (i.e. Google requiring it), why has Airliners.net not implemented one?
An SSL costs $8.99/year and takes about 30 minutes of a developers time to implement onto a website.
Cush wrote:I don't understand why Airliners.net has not yet implemented their SSL? With all of the major changes (i.e. Google requiring it), why has Airliners.net not implemented one?
An SSL costs $8.99/year and takes about 30 minutes of a developers time to implement onto a website.
c933103 wrote:On the support board, they said they are working on it with relatively high priority (on top of other things like bringing the certain aviation photo site back). Probably they would be rolled out soon I guess.
As for the "not secure" tag, it is just a way for Chrome to tell its users to push website administrators into upgrading their sites to use HTTPS. It shouldn't matter as long as you are not logging in to the site (hence typing and transmitting password) via unprotected network connections (like unencrypted wifi). It is not something new to the site, the site is always like this, but it is new to chrome, where chrome's developers (i.e.Google) believe it is needed to use a new way to let users push websites into adopting something more secure.
janders wrote:It seems we are back to http again.
Google Chrome kicking up "Not Secure" warning
airkas1 wrote:I manualy changed the A.net links that were stored in my bookmarks from http to https and that did the trick. I'm now on the secure version.
airkas1 wrote:I manualy changed the A.net links that were stored in my bookmarks from http to https and that did the trick. I'm now on the secure version.
JohnKrist wrote:Moo, HSTS is not fool proof, yes it makes it a bit more difficult but is no match to go around.
Http should be disabled, in IIS it’s a simple server binding however I don’t know what server environment VS uses.
airkas1 wrote:I manualy changed the A.net links that were stored in my bookmarks from http to https and that did the trick. I'm now on the secure version.
scbriml wrote:Still "not secure" for me.
atcsundevil wrote:scbriml wrote:Still "not secure" for me.
Have you tried clearing your cookies? I did that around the time that the site switched to https, and it's never been unsecured for me. I can't even force it to http.
Obviously the site should automatically redirect to https, but that's a different story.
LAXintl wrote:Still have not been able to get https to stick. Site repeatedly http using chrome browser with "not secure" warning.
atcsundevil wrote:Now my browser is showing unsecure, which is the first time that's happened since HTTPS was added. I can't even force it. Curious.