Is Google Captcha serving reCaptcha api.js locally preventing correct behavior?

I recently updated my recaptcha implementation to a newer version of google. My understanding is that some sane portions of users should see captchas that are not standard garbled text / read address photos.

The catchars work correctly in terms of maintenance and give correct answers to user input, but every time I use the widget, I am asked to answer a garbled text question, just like the old reCaptcha.

My question is this: is this the result of a misconfiguration / incorrect implementation on my part, and if so, how can I fix it?

My hypothesis at this point is that this is the effect of serving the gateway api.js file from my own server and not from google directly ... if this is the likely culprit, how does this affect the captcha operation?

Thanks guys!

+3


source to share


1 answer


For the record, the answer was yes. api.js has a magic url in it that changes periodically, so it needs to either be updated very often or served from google servers.



+3


source







All Articles