ReCAPTCHA API URL change

RESOLVED WONTFIX

Status

Cloud Services
Server: Registration
--
blocker
RESOLVED WONTFIX
7 years ago
7 years ago

People

(Reporter: rnewman, Unassigned)

Tracking

({regression})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [php][py=653224][ap=653223])

(Reporter)

Description

7 years ago
Oh dear. All signups currently fail to display a captcha, because we didn't change the URL as described in this message:

http://groups.google.com/group/recaptcha/browse_thread/thread/57baacc2a067035a

We are indeed getting a cert error.

---
The transition involves a very simple change to your code.  Any time
between now and April 11, you need to replace all instances of:
https://api-secure.recaptcha.net/XXX
with:
https://www.google.com/recaptcha/api/XXX

If you don’t make the change before April 11, your users might see SSL
certificate warnings when visiting your site.  (However, the CAPTCHA
should still load normally, unless the user has restrictive security
settings.) 
---

Code is possibly here:

http://mxr.mozilla.org/mozilla-central/source/browser/base/content/syncSetup.js#72


This affects Aurora.
(Reporter)

Comment 1

7 years ago
There's a client component to this (for noScript), but the main issue is a server config, I think.
Component: Firefox Sync: Backend → Server: Registration
QA Contact: sync-backend → reg-server
This blocks everything! All channels, Fx4 and extension on 3.6.x
Severity: critical → blocker
Keywords: regression
Recaptcha has changed their urls. Fixed on reg, now updating account-portal with the fix
PHP code resolved in hg and monkeypatched in production.  Leaving this bug open so we can decide how to clean up and deploy a tag of some sort to get rid of the monkeypatch.
Whiteboard: [php][py=??????][ap=??????]
Whiteboard: [php][py=??????][ap=??????] → [php][py=653224][ap=653223]
That would be the move-over-to-python bug I was just about to file when this happened. I'll get it up after I finish jr's code review.
PHP deprecated, this is the [php] tagged bug, wontfix'ing it.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.