I manage a site that uses recaptcha for registration. As of 2:30 PM PST today the server-side verification of the client's recaptcha response has been failing.
I didn't personally develop this code and I am not sure the name(s) of the features being used.
The client is shown a captcha in which the check a box "I am not a robot" and sometimes they have to additionally check off some pictures of food or something. This is all working fine.
When the client completes registration they post to my server a very long data string "recaptchaResponse" along with their registration data.
{
response: ["03AHJ_Vut3ujeKsjT919rAiYynzpFYE2RIUh0j69vjMfMvmiq397MAT7OxTzgAXJQALWrbUXz....etc"],
secret: ["a_shorter_string_our_secret_code"]
}
The google server has always previously replied with data like this:
{
success: true,
error-codes: []
}
Or sometimes success: false with some errors or etc.
As of 2:30 PM today, google started replying with data like this:
{
"success": true,
"challenge_ts": "2016-02-24T23:25:40Z",
"hostname": "my_servers_hostname"
}
My server is failing to parse this unexpected response into the object it is expecting... users are unable to register.
Is this a known issue? Should I redeploy my server to handle this new data format? Or is this some mistake that will be switched back?