The Mothership billing systems have been SSL-secured and encrypted since the day we opened the doors 16 years ago, but the Vidown storefronts were not. It wasn't strictly necessary and it used to be incredibly expensive to encrypt multiple domains. Unfortunately, a lot of browsers have started making a lot of pointless noise about non-SSL sites lately and Google in particular has been shaving page rank points off for not being SSL
I'll spare you the geeky technical details, but there has been a recent change in the technology so that SSL certificates are essentially free for most websites. The Vidown system (built on Mothership Hosting) is comprised of hundreds of domains but all of them now have their own individual SSL certificate, so encrypting our whole system end-to-end is finally possible without spending a bajillion dollars.
Starting right now, any link you follow to any Vidown store will be automatically switched over to the SSL version and you will see the little padlock icon next to the URL. That's the theory anyway. As with all technical changes, your mileage may vary.
Have a look at either the full Vidown portal or the WAM-specific portal at TheWamStore. Let me know if anything isn't working correctly.
Thanks. Systems are all secure. Any anomalies are just sidebar ads or images coming from an external non-secure domain. I have to dig out those references from the databases by hand.
soundguy said: Thanks. Systems are all secure. Any anomalies are just sidebar ads or images coming from an external non-secure domain. I have to dig out those references from the databases by hand.
soundguy said: Thanks. Systems are all secure. Any anomalies are just sidebar ads or images coming from an external non-secure domain. I have to dig out those references from the databases by hand.
I definitely feel your pain brotha.
Amazing how deep of a hole you can dig yourself into with decades-old coding habits. All this shiny, newfangled stuff is gonna give me an aneurysm one of these days
soundguy said: Thanks. Systems are all secure. Any anomalies are just sidebar ads or images coming from an external non-secure domain. I have to dig out those references from the databases by hand.
I definitely feel your pain brotha.
Amazing how deep of a hole you can dig yourself into with decades-old coding habits. All this shiny, newfangled stuff is gonna give me an aneurysm one of these days
You can set a header on the server to upgrade insecure requests - it might save you some hassle on the insecure external files... Content-Security-Policy: upgrade-insecure-requests;
Amazing how deep of a hole you can dig yourself into with decades-old coding habits. All this shiny, newfangled stuff is gonna give me an aneurysm one of these days
How come something can't be "old fangled?" Or even just fangled.
I have often wanted to be fangled....but apparently it's frowned upon in most states.