"AndrewMachado.com is the best technology blog on the Internet."
-Steve Jobs
Tyler Menezes
· 1 year ago
I'd rather it did throw that error. It's because the SSL cert for Google is only valid for www.google.com, not google.com. If it didn't throw that error, it would mean that anyone could pretend to be https://google.com with no problems. The real WTF is why hasn't Google spend the extra $1000 for a cert without the www?
james
· 1 year ago
1000? laf, they're not that expensive
Tyler D
· 1 year ago
They're pricey for the ultra-secure ones required by companies like Google and Paypal.
OkonX
· 1 year ago
This has happened to me many times... BUT Google Adsense's security certificate is registered for WWW.google.com/adsense NOT google.com/adsense
that's why it keeps coming up...the same thing happens in all browsers
KooperG
· 1 year ago
Isn't that just for httpS, secured (ssl) pages? Which means that your probably manually the (incorrect) link following a visit to a webstore or such, which got not much to do with Google or any mistake on their side. Anyhow, it's still funny :0
Laknath
· 1 year ago
And it's not just about Chrome. Any browser with enough SSL protections will give this error. For example try FF3.
Pavan
· 1 year ago
Look at the error, it specifically states that it is identifying as 'www.google.com', yet you have typed in 'google.com'.
titosmootz
· 1 year ago
Don't blame chrome, you get the same message if you use Firefox.
I guess you dont understand how ssl works, this is working as expected. SSL negotiation happens before HTTP requests are sent, so the server cant read your Host header and send you the correct certificate, so when there are multiple virtual hosts or CNAMEs, your browser correctly points out the hostname mismatch.
This is not funny, google being broken or anything else, but congratulations for convincing a load of digg lamers that this is big news.
susan
· 1 year ago
hahah... sorry - found some amusement in that. Hang in there!!!! :)
PhoenixP3K
· 1 year ago
Same thing happens in Opera 9.6 But still kind of funny?
josef
· 1 year ago
PEBKAC
sdka
· 1 year ago
Check your system time, you dumb ass!
Free xbox 360 Elite
· 1 year ago
Wow that's strange. I wonder why it threw up that error?
Steven
· 1 year ago
That is only because google does not have a security signed certificate for their adsense site. This is normal. Do not pay attention to this article.
Bill
· 1 year ago
nice photoshop work... not
lainie
· 1 year ago
Well. I'm quite glad to see that, for security reasons.
What irks me is that after I've loaded Google Reader, the page crawls - works much better in firefox for me.
Casey
· 1 year ago
fail.
Emposts
· 1 year ago
It means you are being taken to another sever from your local network.. right?
idiotonuni
· 1 year ago
It has done the same to me with blogger
Kreed
· 1 year ago
Lame
Wtf
· 1 year ago
What the fuck are you niggas saying NIGGA NIGGA NIGGA!!!!!!!!!!!
movie fan
· 1 year ago
wow that is crazy... i guess beta testing can't cover everything...
Ryan
· 1 year ago
I am not sure why you find it humorous. When the name of what you typed does not match the CN in the SSL certificate, even if it is off by a single character, you should be warned. Are you suggesting that google should exempt themselves from good SSL practices?
peter
· 1 year ago
the software is hating on itself.
Sean
· 1 year ago
That is funny... Saw same thing on a few other sites as well...
Right, google's adsense ssl is registered with the www subdomain. bunch of morons you all are.
greg
· 1 year ago
Weird. Whats even weirder, if you take a second more and type the "www." in front of google.com/adsense, it works just fine.
Daniel Dumas
· 1 year ago
it happens to me also before i also laugh hehe but i noticed that i forgot to type the www, adsense do not work without the www
John
· 1 year ago
It's supposed to be google.com/adsense retard
kekamama
· 1 year ago
yep u r correct dude..i faced same problem
Laknath
· 1 year ago
Yes, this is a common thing in SSL practises. But what we usually do when implementing SSL is either,
1) redirect (301) www.domain.com to domain.com to avoide this and just use SSL for domain.com or 2) Use a wildcard SSL to protect all used sub domains.
It's weird Google don't do it with such a massive product like adSense.
.
· 1 year ago
it is your fault for not put the www. infront of google.com, idiot
Sam
· 1 year ago
probably because they had an outdated/incorrect security certificate. ooooh, big whoop, I see this every day, its not that big of a deal.
james
· 1 year ago
USER ERROR! :)
Michael
· 1 year ago
https?
dumbass.
SoManyLemmings
· 1 year ago
why do so many people have to reply with the same response? no crap the www.google.com and google.com are different.
and it is funny...that google didn't get a cert for non www...
All Comments
-Steve Jobs
BUT
Google Adsense's security certificate is registered for WWW.google.com/adsense
NOT google.com/adsense
that's why it keeps coming up...the same thing happens in all browsers
Anyhow, it's still funny :0
google.com uses an invalid security certificate.
The certificate is only valid for www.google.com
(Error code: ssl_error_bad_cert_domain)
http://www.mysite.com and
http://mysite.com are not the same site.
Either a redirect didn't happen or Google didn't get a *.google.com SSL cert. Either way, it is still a good thing.
https://verisign.com/
https://microsoft.com/
https://geotrust.com/
I guess you dont understand how ssl works, this is working as expected. SSL negotiation happens before HTTP requests are sent, so the server cant read your Host header and send you the correct certificate, so when there are multiple virtual hosts or CNAMEs, your browser correctly points out the hostname mismatch.
This is not funny, google being broken or anything else, but congratulations for convincing a load of digg lamers that this is big news.
But still kind of funny?
What irks me is that after I've loaded Google Reader, the page crawls - works much better in firefox for me.
Saw same thing on a few other sites as well...
___________________________
Free Digital Signage from http://www.MediaSignage.com
1) redirect (301) www.domain.com to domain.com to avoide this and just use SSL for domain.com
or
2) Use a wildcard SSL to protect all used sub domains.
It's weird Google don't do it with such a massive product like adSense.
dumbass.
and it is funny...that google didn't get a cert for non www...