> This is far from ideal as we use the ASP.NET server control, which
> appears to have the URI that is changing hardcoded into it.

> Can you tell me when the .NET control will be updated as it appears to
> not have been updated since Dec 14 2010?

> Failing that where can I get the source code for the .NET control so
> that I can make the change myself?

> It will take substantial rework to out production system to use
> another method, so that's not really an option.

> geedubb

> On Apr 12, 8:40 pm, reCAPTCHA Support <supp...@recaptcha.net> wrote:
>> We have temporarily rolled back this change. However we will be
>> re-enabling it soon (within the next couple days.)

>> Colin

>>> Hi - We missed the notice originally. This morning users of our system
>>> were getting the ssl warning and no recaptcha. But of late that
>>> problem seems to have gone and the users are able to see the recaptcha
>>> widget all right and the ssl warning has gone too. Have you reverted
>>> back to the old URL ? Also, if that is the case can you let me know
>>> what is the 'drop-dead' date by which we need to implement the URL
>>> change so as not to have our users encounter the ssl warning.

>>> On Apr 12, 8:49 am, reCAPTCHA Support <supp...@recaptcha.net> wrote:
>>>> FYI, we are now purposely serving an expired SSL certificate for
>>>> api-secure.recaptcha.net. This is expected behavior -- we are serving
>>>> this as a "warning" to sites which are still using the legacy SSL
>>>> URLs. Sometime in the near future (roughly a week or two) it will be
>>>> "more wrong" -- most likely, you'll get the cert forwww.google.com
>>>> instead of api-secure.recaptcha.net.

>>>> Colin

>>>> On Tue, Apr 12, 2011 at 9:11 AM, reCAPTCHA Support

>>>> <supp...@recaptcha.net> wrote:
>>>>> This is starting now.

>>>>> Colin

>>>>> On Mon, Apr 11, 2011 at 6:30 PM, reCAPTCHA Support
>>>>> <supp...@recaptcha.net> wrote:
>>>>>> Reminder: we will be making this change later this week -- most likely
>>>>>> tomorrow.  If your site still uses SSL over the legacy servers (api-
>>>>>> secure.recaptcha.net), your users will soon start to see SSL warnings
>>>>>> in their browsers.

>>>>>> Best,
>>>>>> Colin

>>>>>> On Mar 8, 4:35 pm, reCAPTCHA Support <supp...@recaptcha.net> wrote:
>>>>>>> Hi reCAPTCHA users,

>>>>>>> In April, we will begin to turn down thelegacyURL for reCAPTCHA's
>>>>>>> HTTPS API.  If your site uses reCAPTCHA overSSL, you will need to
>>>>>>> make a minor code change before April 11.

>>>>>>> If your site does not load the reCAPTCHA challenge API overSSL, you
>>>>>>> do not need to make any changes.  You can tell if you’re usingSSLby
>>>>>>> looking at the source of your page(s) which contain reCAPTCHA and
>>>>>>> seeing whether you use "https://api-secure.recaptcha.net" anywhere.

>>>>>>> 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 seeSSL
>>>>>>> certificate warnings when visiting your site.  (However, the CAPTCHA
>>>>>>> should still load normally, unless the user has restrictive security
>>>>>>> settings.)

>>>>>>> Most commonly, this shows up as a call to the reCAPTCHA challenge API
>>>>>>> on the page that contains reCAPTCHA, such as:

>>>>>>> <script src="https://api-secure.recaptcha.net/challenge?k=XXXYYYZZZ"></
>>>>>>> script>

>>>>>>> This call needs to change to something like this:

>>>>>>> <script src="https://www.google.com/recaptcha/api/challenge?
>>>>>>> k=XXXYYYZZZ"></script>

>>>>>>> ... everything after the /challenge can remain exactly as it was.

>>>>>>> Another thing to look for is if you're including the reCAPTCHA
>>>>>>> JavaScript over HTTPS.  Code that looks like:

>>>>>>> <script src="https://api-secure.recaptcha.net/js/recaptcha.js"></
>>>>>>> script>
>>>>>>> or
>>>>>>> <script src="https://api-secure.recaptcha.net/js/recaptcha_ajax.js"></
>>>>>>> script>

>>>>>>> Would need to change to:
>>>>>>> <script src="https://www.google.com/recaptcha/api/js/recaptcha.js"></
>>>>>>> script>
>>>>>>> or
>>>>>>> <script src="https://www.google.com/recaptcha/api/js/
>>>>>>> recaptcha_ajax.js"></script>

>>>>>>> We're sorry for the inconvenience; please let us know if you have any
>>>>>>> questions or concerns about making this change.  We will be contactingSSL-using site owners individually to let them know about this change;
>>>>>>> however we wanted to post in the public forum as well, since we may
>>>>>>> not have up-to-date contact information for all sites.

>>>>>>> Best,
>>>>>>> Colin & the rest of the reCAPTCHA team

>>>>>> --
>>>>>> You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
>>>>>> To post to this group, send email to recaptcha@googlegroups.com.
>>>>>> To unsubscribe from this group, send email to recaptcha+unsubscribe@googlegroups.com.
>>>>>> For more options, visit this group athttp://groups.google.com/group/recaptcha?hl=en.

>>>>> --
>>>>> reCAPTCHA: stop spam, read books
>>>>> http://www.google.com/recaptcha

>>>> --
>>>> reCAPTCHA: stop spam, read bookshttp://www.google.com/recaptcha-Hide quoted text -

>>>> - Show quoted text -

>>> --
>>> You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
>>> To post to this group, send email to recaptcha@googlegroups.com.
>>> To unsubscribe from this group, send email to recaptcha+unsubscribe@googlegroups.com.
>>> For more options, visit this group athttp://groups.google.com/group/recaptcha?hl=en.

>> --
>> reCAPTCHA: stop spam, read bookshttp://www.google.com/recaptcha- Hide quoted text -

>> - Show quoted text -

> --
> You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
> To post to this group, send email to recaptcha@googlegroups.com.
> To unsubscribe from this group, send email to recaptcha+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.