'Google has announced web pages using HTTP and not HTTPS will be shown as NOT SECURE by Chrome.
What is the best way to update a regular 1.5.6.4 site to make it compliable with this please?
The site already resolves with a https:// both sides of the store
Well, just check on first, what still missing, before this can be answerred.
Ernie
---
https://www.whynopadlock.com/
Ernie
---
https://www.whynopadlock.com/
My Github OC Site: https://github.com/IP-CAM
5'200 + FREE OC Extensions, on the World's largest private Github OC Repository Archive Site.
Thanks Ernie,
Did the test above and all came out okay except this..
--------------------
You currently have TLSv1 enabled.
This version of TLS is being phased out. This warning won't break your padlock, however if you run an eCommerce site, PCI requirements state that TLSv1 must be disabled by June 30, 2018.
Did the test above and all came out okay except this..
--------------------
You currently have TLSv1 enabled.
This version of TLS is being phased out. This warning won't break your padlock, however if you run an eCommerce site, PCI requirements state that TLSv1 must be disabled by June 30, 2018.
Who is online
Users browsing this forum: Bing [Bot] and 118 guests