Any chance of implementing the SSL properly

As per the title, could this please be implemented properly so that it's actually worth having?

Bumping thread

I've explained this a few times for them. SSL on a website is designed to protect its users, it's the little padlock that you see in the address bar, or the green secure logo in the address bar in chrome. It means that all the traffic is encrypted to the end server and not visible to everyone along the way - this is a very real issue. It's trivial to sit in a cafe on a Wi-Fi network and intercept and modify all traffic that isn't encrypted - so as a rule of thumb if you haven't connected to a website on an https link and have a padlock assume that everything you send (including passwords) can be read by anyone, furthermore anyone can insert malicious things into the page and you'd never know.

The reason that this site doesn't have a padlock/secure icon even though you connect using an https url is that only some content is encrypted - not all of it. The technical term for this is mixed content https://www.troyhunt.com/understandi...mixed-content/

To see how the address bar should look, compare it to mrexcel (where it's implemented properly). This really is basic stuff that just isn't being done.

If a more commercial reason is required (rather than protecting your users/customers) is that Google search is penalizing sites that have either not implemented ssl or or have not implemented it properly.

This is particularly concerning since the site takes payments for commercial services, it's quite possivle for an attacker to send users to a malicious site designed to capture their payment details. For this reason, in case anyone out there doesn't know, never, ever buy things from a website that does not have either a padlock in the taskbar or a green secure icon. It's also why some browsers have started displaying a not secure warning in the address bar

I've pm'ed and I will find you some posts if you like