IMPORTANT: More changes to SSL certificates for https://api-secure.recaptcha.net

瀏覽次數:2,604 次
跳到第一則未讀訊息

reCAPTCHA Support

未讀,
2011年5月2日 下午6:26:202011/5/2
收件者:reCAPTCHA Announcements
Hi all,

If you don't use reCAPTCHA over SSL, or if you have already changed
your code to use the new URLs (https://www.google.com/recaptcha/
api/...), you can stop reading now -- this change won't affect you.

If you haven't changed your URLs yet, users visiting your site will
get a slightly different error. Instead of getting an expired
certificate for api-secure.recaptcha.net, users will instead get a
valid certificate for the wrong domain: www.google.com. Since users
were *already* getting a bogus certificate for api-
secure.recaptcha.net, we don't consider this a breaking change; it's
just trading one kind of brokenness for an (arguably more accurate)
kind of brokenness.

So: this ought not to affect anyone who wasn't already affected by the
previous change, but we figured we'd announce it here anyways, so that
people are aware of the different error message that might show up in
users' browsers.

The announcement of the previous change can be found here:
http://groups.google.com/group/recaptcha-announce/browse_thread/thread/c1ff6844420c9e63

Best,
Colin (& the rest of the reCAPTCHA team)

reCAPTCHA Support

未讀,
2011年5月3日 下午3:04:412011/5/3
收件者:reCAPTCHA Announcements
This is now complete.
回覆所有人
回覆作者
轉寄
0 則新訊息