This is just a quick post to hopefully stem the tide of people commenting (in blog comments and Twitter messages) saying that this blog is broken when it comes to CAPTCHAs and Chrome. I know, but there’s nothing I can do about it – I don’t run the software on the blog. I haven’t looked into why it’s not working… if you open the image in a new tab, it displays that fine. Weird, but such is life… I’m hoping that an update to either Community Server or Chrome will fix it eventually.
- Comment
- Reblog
-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
Jon Skeet's coding blog 
Seeing if this works.
LikeLike
Nope. Doesn’t work here either. I also notice that Chrome omits the HTTP:// part in the URL, but it does this for all URL’s, except the secure ones.
Opening the Capcha image in a separate window does work, though. And it also exposes a minor flaw: when you refresh the image often enough, the image might become machine-readable through OCR. That’s because it draws a new image every time with the same digits over and over again. Thus a machine coudl read it by retrieving the Capcha about 25 times, do an OCR read on each image and then choose the best guess from all those attempts.
So, your Capcha isn’t too secure. Sorry to be the bearer of bad news…
LikeLike
It seems to be working on Chrome on Linux.
LikeLike
Thanks for the information on the capatcha! Did chrome ever get that fixed?
LikeLike
Chrome 7.0.517.0 dev
LikeLike
Susan here… yup it’s just in Chrome.
We don’t get updates anymore to community server but I’ll ask the guy who helped us with the captcha.
LikeLike
Works fine on Chrome 8.0.552.5 on 64-bit Windows 7. Though the text in the captcha itself is very hard to read occasionally.
LikeLike