I use https://maps.google.co.nz as the start page for Google maps but using IE7 I always get “There is a problem with this website’s security certificate.” on first landing there. It’s because the certificate is issued to *.google.com, not *.google.co.nz. I’m surprised this is happening and that Google hasn’t sorted it out. Does it happen with *.google.ca or *.google.com.au?
Sometimes I forget to leave the last ‘S’ off for savings and end up overpaying. :mad:
I see what you did there, Rhythmdvl. How DO you sleep at night?
-D/a
Not exactly a hijack, virus, or malware… but very frustrating. A site you have been too hijacked your browser to slightly alter the way google acts. Some variants simply put https… others additional stuff at the end of the URL.
It’s simple to fix.
Go to Firefox help…
Choose Troubleshooting Information…
Click on Reset Firefox.
It will save all your bookmarks etc.
After doing this, if your home page should be http://google.com it will be.
The main bother to all this is that the actual search field loses it’s automatic “focus”, meaning when you go there the cursor was not left in the search field but at the end of the URL. ANNOYING.
Resetting as above does the trick.
Sorry to repeat if it has been said above, but the ‘S’ is a very good thing. It means that all communications between your computer and where you are trying to go is strongly encrypted and cannot be read by any sites other than the one you are trying to read (the URL).
It is not a result of a virus or malware.
Bob
I assumed it was a reaction to revelations about the NSA and similar snooping.
HTTPS simply means the connection between you and the target is encrypted. That way, your company’s firewall, the police snooping on your line, of the NSA, cannot tell what you are searching for and what you click on (unless that takes you to an outside http site). Everything you do within Google is private.
I find it very annoying, as mentioned, when I retype addresses but leave the “https://www.” part. for many websites, there is no https or it takes you to a different place than http.
Facebook and such will use https because you are logged in. Part of the login is the secure connection, to ensure that the data they receive for that session is from only you. (Otherwise, a clever hacker might start spoofing your address once you entered a password).
https uses the public/private key crypto - they send you a public key, you use it to send data, that only their private key can decode; decoding the public key encoding is almost impossible without the private key, so it’s fairly secure. Others intercepting the transmission cannot tell what you sent.
This thread was started in 2011.