7

This question already has an answer here:

The image that appears above the captcha seems to be broken.

Eeek!

(You can also view a live version of this)

This appears to affect other sites as well, even though they use different images.

Note that if you view the image URL directly and accept the SSL warning, all the images may appear to start working for you - but restarting your browser will reveal broken images again.

I actually encounter this captcha quite frequently due to writing up my answers in an external editor, and then pasting them in as a new response. I just started noticing the broken image today.

marked as duplicate by hims056, Manishearth, Martijn Pieters, ben is uǝq backwards, animuson Jul 6 '13 at 16:20

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • I think this one is worthy of an "Eeek!" – Andrew Barber Jul 6 '13 at 5:04
  • 1
    The possible-duplicate is closed as by-design - but it doesn't seem to have actually addressed the fact that the wrong URL is still being used. – jcsanyi Jul 6 '13 at 5:06
  • @AndrewBarber - Or Eeek! Is it by design? – hims056 Jul 6 '13 at 5:06
  • @hims056 I didn't find that question when I searched, thanks. I interprete it as saying the certificate issues are by-design and pointed to the OP looking at the wrong URL - but it still didn't address the fact that the wrong URL is being used on the live sites. – jcsanyi Jul 6 '13 at 5:08
  • 2
    @AndrewBarber Updated with a freehand circle and and an Eeek! – jcsanyi Jul 6 '13 at 5:14
  • This is now Perfection! – Andrew Barber Jul 6 '13 at 5:14
  • 1
    See: this is why we can't have nice things. The developers should've used jQuery to detect if the image loaded. If it can't, then switch it to a base64 encoded version saved in the JS file itself. If the JS can't be loaded, just use jQuery to fix that! – Cole Johnson Jul 6 '13 at 5:38
  • 1
    This looks like another victim of the SSL project. I really think it needs to be added to the wheel of blame. – jcsanyi Jul 6 '13 at 5:46
  • @jcsanyi: I did not mean to imply that the OP of that report was using the wrong URL. I was pointing out that the real bug was that the page is using the wrong URL. Why it was marked as status-bydesign is beyond me, I'll flag the post. – Martijn Pieters Jul 6 '13 at 11:21