Recaptcha is down?
John
http://www.google.com/recaptcha/api/js/recaptcha_ajax.js
This is killing site traffic. :(
Do you guys have a status page?
reCAPTCHA Support
Bad push on our end; we're currently reverting it.
> --
> You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
> To post to this group, send email to reca...@googlegroups.com.
> To unsubscribe from this group, send email to recaptcha+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
>
>
--
reCAPTCHA: stop spam, read books
http://recaptcha.net
Matt G.
to clients? My team is weighing the cost/risk of temporarily removing
reCAPTCHA from all affected sites until this is resolved. It would be
helpful to know if we can expect corrected JS in 10 minutes, one hour,
etc.
Thank you for correcting this issue.
On Sep 17, 3:29 pm, reCAPTCHA Support <supp...@recaptcha.net> wrote:
> Hi,
>
> Bad push on our end; we're currently reverting it.
>
> On Fri, Sep 17, 2010 at 4:00 PM, John <sma...@gmail.com> wrote:
> > When I download the ajax JS file, it returns a 1-line blank file.
> >http://www.google.com/recaptcha/api/js/recaptcha_ajax.js
>
> > This is killing site traffic. :(
>
> > Do you guys have a status page?
>
> > --
> > You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
> > To post to this group, send email to reca...@googlegroups.com.
> > To unsubscribe from this group, send email to recaptcha+...@googlegroups.com.
--
Matt
reCAPTCHA Support
out to be in error.
Colin
> For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
reCAPTCHA Support
All should be back to normal now. We'll continue to keep an eye on
it, but please let me know if you see any persisting issues with the
reCAPTCHA AJAX API.
Some browsers may have cached the empty version of recaptcha_ajax.js,
but if those folks hit shift-reload all should be fine.
Thanks,
Colin
Bill Orcutt
reCAPTCHA Support
Can you please try:
1) Going to http://www.google.com/recaptcha/api/js/recaptcha_ajax.js
and holding down "shift" while hitting the reload button?
2) Going to https://www.google.com/recaptcha/api/js/recaptcha_ajax.js
and seeing if you get a non-blank page.
Are you behind any proxies or anything else that might be erroneously
caching the blank version of the Javascript?
Thanks!
Colin
Ed
i tried a forced refresh as well
Bill Orcutt
Seeing a 200 response code from both.
> Can you please try:
>
> 1) Going tohttp://www.google.com/recaptcha/api/js/recaptcha_ajax.js
>
> Are you behind any proxies or anything else that might be erroneously
> caching the blank version of the Javascript?
>
> Thanks!
>
> Colin
>
>
>
>
>
> On Fri, Sep 17, 2010 at 5:11 PM, Bill Orcutt <orc...@gmail.com> wrote:
> > I'm still seeing an empty response
>
> >http://www.google.com/recaptcha/api/js/recaptcha_ajax.js
>
> > On Sep 17, 2:01 pm, reCAPTCHA Support <supp...@recaptcha.net> wrote:
> >> Hi,
>
> >> All should be back to normal now. We'll continue to keep an eye on
> >> it, but please let me know if you see any persisting issues with the
> >> reCAPTCHA AJAX API.
>
> >> Some browsers may have cached the empty version of recaptcha_ajax.js,
> >> but if those folks hit shift-reload all should be fine.
>
> >> Thanks,
> >> Colin
>
> > --
> > You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
> > To post to this group, send email to reca...@googlegroups.com.
> > To unsubscribe from this group, send email to recaptcha+...@googlegroups.com.
jennyw
http://www.google.com/recaptcha/api/js/recaptcha_ajax.js?234
It brings up code. Not sure if it works … we're going to try it out
soon.
Ed
> Can you please try:
>
> 1) Going tohttp://www.google.com/recaptcha/api/js/recaptcha_ajax.js
>
> Are you behind any proxies or anything else that might be erroneously
> caching the blank version of the Javascript?
>
> Thanks!
>
> Colin
>
>
>
> On Fri, Sep 17, 2010 at 5:11 PM, Bill Orcutt <orc...@gmail.com> wrote:
> > I'm still seeing an empty response
>
> >http://www.google.com/recaptcha/api/js/recaptcha_ajax.js
>
> > On Sep 17, 2:01 pm, reCAPTCHA Support <supp...@recaptcha.net> wrote:
> >> Hi,
>
> >> All should be back to normal now. We'll continue to keep an eye on
> >> it, but please let me know if you see any persisting issues with the
> >> reCAPTCHA AJAX API.
>
> >> Some browsers may have cached the empty version of recaptcha_ajax.js,
> >> but if those folks hit shift-reload all should be fine.
>
> >> Thanks,
> >> Colin
>
> > --
> > You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
> > To post to this group, send email to reca...@googlegroups.com.
> > To unsubscribe from this group, send email to recaptcha+...@googlegroups.com.
reCAPTCHA Support
1) What country are you located in?
2) What browser / OS are you using?
3) Do you get a non-blank page if you do Jenny's trick:
http://www.google.com/recaptcha/api/js/recaptcha_ajax.js?1234
Thanks,
Colin
> For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
Mark Ketchum
Ed
if i cache bust my site, captcha still does not appear
reCAPTCHA Support
After cache-busting the ajax link and then shift-reloading your site,
does it show up? Can you send a link to your site that shows an AJAX
reCAPTCHA so I can take a look at it? Thanks.
Colin
> For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
Mark Ketchum
1. U.S.A. (San Francisco, CA)
2. Win7/64 & Ubuntu ??, Firefox 3.6.8, IE 8.0, Chrome 6.0
3. Jenny's trick works but normal still comes up blank
Ed
Firefox & IE7 / windows xp
Bill Orcutt
1. U.S.A. (San Francisco, CA)
Mark Ketchum
On Sep 17, 2:39 pm, Bill Orcutt <orc...@gmail.com> wrote:
> Still blank response onhttp://www.google.com/recaptcha/api/js/recaptcha_ajax.js
ajc
this if I don't have to. Will this be fixed sometime soon?
Adam
reCAPTCHA Support
looking into possible issues with caching on our (reCAPTCHA's) end.
In the worst case, the browsers should only cache the faulty JS file
for one hour (according to our cache-control headers), but not all
browsers are well-behaved...
Anyhow, I'm still looking into it but don't have anything concrete to
report at the moment.
Colin
> For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.
cali_jonny
Bill Orcutt
ajc
recaptcha_ajax.js file. I agree that this is not a browser caching
issue. I would guess that the file is cached on content distribution
servers.
reCAPTCHA Support
> recaptcha_ajax.js file. I agree that this is not a browser caching
> issue. I would guess that the file is cached on content distribution
> servers.
That's my best guess as well, but I actually can't make that change
myself. I've escalated to the folks at Google who handle that sort of
stuff, and will update here when I get an ETA from them or
confirmation that it's been cleared from all the caches on Google's
end.
In the meantime, if this is still affecting your site, changing your
code to add the ?1234 to the end of the recaptcha_ajax.js URL (as
suggested earlier in the thread) is a suitable workaround.
Colin
Mark Ketchum
reported an hour ago) and it still works. The original code (still up
on a test server) remains non-working.
What is the risk that the tricked code is gonna break when a real fix
is made? I'd rather leave this alone for a while.
And someone responded to me instead of the list:
>RO (Bv) - Win7 32 / WinXP 32 / Win2003 64 - IE6/IE7IE8/Firefox 3.5
>Http return empty file
>Https work fine
>Trick work fine
But https does NOT work for me.
reCAPTCHA Support
> is made? I'd rather leave this alone for a while.
The "tricked code" won't break when the real fix is made. Adding the
?1234 at the end just gets the latest version of the file (as opposed
to the version which is cached somewhere).
Colin
vegan...@gmail.com
Sent from a mobile device ... Please excuse typos
reCAPTCHA Support
We pushed a change a short while ago that fixes the issue if you are
using the legacy recaptcha.net JavaScript URL
(http://api.recaptcha.net/js/recaptcha_ajax.js). If you are using the
recaptcha.net URL for your Javascript, all should now be working fine.
The change for www.google.com/recaptcha/api/js/recaptcha_ajax.js will
take longer; still no ETA on that (sorry.)
In the meantime, if you're still using the broken URL, the fix
presented earlier in this thread will work (link to
http://www.google.com/recaptcha/api/js/recaptcha_ajax.js?1234) or you
can change your link to the older URL
(http://api.recaptcha.net/js/recaptcha_ajax.js if your site uses HTTP,
https://api-secure.recaptcha.net/js/recaptcha_ajax.js if your site
uses HTTPS.)
Thanks everyone for your understanding.
Colin
--
Ed
thanks
GB
returning a blank page.
-GB.
i-imagine
ReCAPTCHA does NOT return ANYTHING. from:
http://www.google.com/recaptcha/api/js/recaptcha_ajax.js
But it works FINE using:
http://api.recaptcha.net/js/recaptcha_ajax.js
YES! I AM SHOUTING AS LOUDLY AS POSSIBLE WITH THIS FORUM'S FORMATTING!
reCaptcha is now looking like an amateurish, part-time, casual
project.that was acquired for the sole interest of collecting more
data on web surfer's habits.
Free or paid, in today's world if the uptime and reliability isn't
maintained then it is clear that the owners have abandoned it. What a
shame.
It is very possible that 100's of websites are using AJAX recaptcha
with my Coppermine Photo Gallery plugins. Gee...I can not wait until
those trouble reports start rolling in.
What do I tell them? Unreadable characters one week - unreachable
servers in the next weeks? What surprises will be next?
If the owners TRULY have no interest, then they should make their
intention clear instead of recaptcha being left to die slowly.....
THIS IS UNACCEPTABLE
Joe Carver
reCAPTCHA Support
> project.that was acquired for the sole interest of collecting more
> data on web surfer's habits.
Please don't assume malicious things about us! Our privacy policy as
a Google product is actually significantly stronger than it was when
we were an independent project.
Please see: http://www.google.com/recaptcha/policy
"Other than these end-user-supplied solutions, any data collected from
the sites that use reCAPTCHA will be used only to provide, maintain,
protect, and improve reCAPTCHA and other Google anti-spam services."
In non-lawyer-speak, that basically means "we don't share data with
anyone else at Google except for spam-prevention".
I've been working on reCAPTCHA full-time for over three years, and do
still care strongly about reCAPTCHA; however with the change to Google
infrastructure, there are now some things that are out of our control,
and unfortunately this is one of those things, so it's just as
frustrating to *me* that this hasn't been fixed sooner.
> Free or paid, in today's world if the uptime and reliability isn't
> maintained then it is clear that the owners have abandoned it. What a
> shame.
From our own end we provided a workaround rapidly; unfortunately the
bad code is cached in Google's CDN and we don't have the permission to
flush it out. Unfortunately, the CDN issue probably won't be fixed
till Monday. :( I'm sorry to be the bearer of bad news, so for now
please use the workaround if you can. After implementing the
workaround for api.recaptcha.net/js/recaptcha_ajax.js, we fixed the
issue for >90% of the AJAX API users (who in turn are a small fraction
of reCAPTCHA's overall users).
We'll be adding tests in the future so that it's not possible for us
to push a binary with empty Javascript files. (We're still not sure
how this happened in the first place, since we've not touched the
Javascript files in over a month; something really bizarre must have
happened.)
Colin
i-imagine
as
a Google product is actually significantly stronger than it was when
we were an independent project"
would be
nothing wrong with complementing a businesses' interest with the offer
of
a free service on the side as long as the interest was made clear.
It is frustrating to see a once rock solid, reliable service go awry.
I am sure best efforts are being made. I plan to still use and promote
the use of reCaptcha.
d07.RiV
still returns blank.
I'm using Chrome, but Firefox is giving the same error (and clearing
cache doesn't help). Is there a possibility that the page was cached
somewhere deeper in the system?
I do not own the website I'm trying to post at so I can't change the
site code (and I can't post on their support forums for the same
reason).
Bill Orcutt
Mark Ketchum
to host that bit of javascript on our own servers, and are advised to
rely on third-party (reCaptcha.net, now Google) servers? And the no-
self-hosting advisory is supposedly to assure better reliability? This
doesn't add up.
Maybe after this incident, the powers-that-be could re-evaluate the
hosting advice on that bit of script.
Cuz it seems to me right now, that the obvious way to improve chances
of a good copy of the google-hosted script is to use
"recaptcha_ajax.js?[server-generated-random-number]" for grabbing the
copy.
On Sep 18, 9:00 am, Bill Orcutt <orc...@gmail.com> wrote:
> http://www.google.com/recaptcha/api/js/recaptcha_ajax.jsis working now for me...
> On Sep 18, 2010, at 8:49 AM, d07.RiV wrote:
>
GB
It returns a blank page.
-GB.
reCAPTCHA Support
www.google.com/recaptcha/api/js/recaptcha_ajax.js should now be the
correct (non-empty) file everywhere; the bad entry is finally cleared
out of the cache. Let us know if you're still experiencing any sort
of problem.
We've added testing code that will ensure that this problem won't
recur in the future.
(If you're interested, the root cause was a change in our JavaScript
compiler; the JS compiler created a blank output file for our input
file, without giving any sort of warning. We added a unit test which
sanity-checks the compiler output. Also, we've fixed the caching so
that any bad push in the future won't cache a bad file for a
potentially-indefinite period of time.)
Sorry again to everyone who was affected by this issue.
Colin