Certificate conflict. The certificate is for the www version of the URL. Probably you typed google.com/adsense instead of http://www.google.com/adsense
Joost, totally agree is very annoying. At least in FF3 I could make a permanent exception and get rid of the annoyance but in Chrome that’s not possible for now.
Firewall Script I'm going to do a full write up on this, but I have been testing this out on a blog, that's been hacked and DDOS a few times over the last 6 months, why do people feel I want to host their Malware, why don't I just update WP time and effort I guess
Anyway I had been looking for a solution that i can install on a shared box that that I didn't have root access on.
Anyway My test is coming to an end, and I going to try and score a deal on a multiple domain license, or even try and buy a lump of the company lol
6 Comments | Leave a comment »
Wow… that’s… interesting? Never have seen that before?
Certificate conflict. The certificate is for the www version of the URL. Probably you typed google.com/adsense instead of http://www.google.com/adsense
All well Razvan, but it shouldn’t be that hard to redirect FIRST and THEN throw you onto https.
Joost, totally agree is very annoying. At least in FF3 I could make a permanent exception and get rid of the annoyance but in Chrome that’s not possible for now.
And the fact that it is Google! You would think they would implement the redirect correctly!
There are some related and similar issues if you ask for http: when the URL you need should be https: and vice-versa.