> 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

<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 at http://groups.google.com/group/recaptcha?hl=en.

<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 at http://groups.google.com/group/recaptcha?hl=en.

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

> 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 -

> 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 at http://groups.google.com/group/recaptcha?hl=en.

> 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 -

> Hi reCAPTCHA users,

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

> If your site does not load the reCAPTCHA challenge API over SSL, you
> do not need to make any changes.  You can tell if you’re using SSL by
> 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 see SSL
> 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 contacting
> SSL-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

> Hi

> 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.

> Is there some way for us to get notified about important changes like
> this without following this whole newsgroup? Your blog hasn't been
> updated in almost a year, and I couldn't find any email list to
> subscribe to, either.

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

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

> To clarify Adrian's comment,

> The .NET control from last December:http://code.google.com/p/recaptcha/downloads/detail?name=recaptcha-do...
> already used the new URLs. If you are use version 1.0.5, it should work.

> Colin

> Hi All

> Is there a new java jar file available to download. The version i have
> recaptcha4j-0.0.7.zip still pointed to old URL.

> Thanks In advance

> Suri

> On Apr 13, 1:48 pm, reCAPTCHA Support <supp...@recaptcha.net> wrote:

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

> > To clarify Adrian's comment,

> > The .NET control from last December:http://code.google.com/p/recaptcha/downloads/detail?name=recaptcha-do...
> > already used the new URLs. If you are use version 1.0.5, it should work.

> > Colin

> Hello,

> This is an extremely painful change that I hope you will reconsider.  Our software serves thousands of nonprofit organizations with millions of users. We implement reCAPTCHA on our donation forms for security, and an invalid certificate warning means our nonprofit clients are losing donations because donors won’t enter credit card information on an unsecure page.

> We are in the process of updating all versions of our software, but it is unreasonable for us to upgrade thousands of clients “within the next couple days”, especially if we don’t even control the servers they’re running on.  I would strongly encourage and appeal to you to extend the “rollback” for a period of 3-6 months (or longer) in order to give us a chance to properly fix, test, and update our products, and give our clients time to apply those updates.  

> tjengine
> --
> 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.

> AFAIK the change has been announced since late last year.

> ---
> Adrian Godong

> On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

> Hello,

> This is an extremely painful change that I hope you will reconsider.  Our
> software serves thousands of nonprofit organizations with millions of users.
> We implement reCAPTCHA on our donation forms for security, and an invalid
> certificate warning means our nonprofit clients are losing donations because
> donors won’t enter credit card information on an unsecure page.

> We are in the process of updating all versions of our software, but it is
> unreasonable for us to upgrade thousands of clients “within the next couple
> days”, especially if we don’t even control the servers they’re running on.
> I would strongly encourage and appeal to you to extend the “rollback” for a
> period of 3-6 months (or longer) in order to give us a chance to properly
> fix, test, and update our products, and give our clients time to apply those
> updates.

> tjengine

> --
> 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.

>  --
> 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.

> Not even that late - it was announced June 30th 2010.

> <http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

> It's not as if it should be a complete surprise to anyone.

> If 9 months is insufficient time to roll out this sort of thing, I'm failing
> to see how a further "3-6 months" is going to help.

> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <adrian.god...@gmail.com>wrote:

> > AFAIK the change has been announced since late last year.

> > ---
> > Adrian Godong

> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

> > Hello,

> > This is an extremely painful change that I hope you will reconsider.  Our
> > software serves thousands of nonprofit organizations with millions of users.
> > We implement reCAPTCHA on our donation forms for security, and an invalid
> > certificate warning means our nonprofit clients are losing donations because
> > donors won’t enter credit card information on an unsecure page.

> > We are in the process of updating all versions of our software, but it is
> > unreasonable for us to upgrade thousands of clients “within the next couple
> > days”, especially if we don’t even control the servers they’re running on.
> > I would strongly encourage and appeal to you to extend the “rollback” for a
> > period of 3-6 months (or longer) in order to give us a chance to properly
> > fix, test, and update our products, and give our clients time to apply those
> > updates.

> > tjengine

> > --
> > 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.

> >  --
> > 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.

> --
> PJH

On Wed, Apr 13, 2011 at 12:58, TG <ashoktheg...@gmail.com> wrote:
> Hi All

> recaptcha4j-0.0.7.zip present at the location (http://code.google.com/
> p/recaptcha4j/downloads/detail?name=recaptcha4j-0.0.7.jar&can=2&q=)
> still contains the URLs of the following format like "http://
> api.recaptcha.net", "https://api-secure.recaptcha.net", "http://api-
> verify.recaptcha.net/verify".
> Its still not updated.

> Thanks
> TG

> On Apr 13, 3:31 pm, PJH <pauljherr...@gmail.com> wrote:
>> Not even that late - it was announced June 30th 2010.

>> <http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

>> It's not as if it should be a complete surprise to anyone.

>> If 9 months is insufficient time to roll out this sort of thing, I'm failing
>> to see how a further "3-6 months" is going to help.

>> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <adrian.god...@gmail.com>wrote:

>> > AFAIK the change has been announced since late last year.

>> > ---
>> > Adrian Godong

>> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

>> > Hello,

>> > This is an extremely painful change that I hope you will reconsider.  Our
>> > software serves thousands of nonprofit organizations with millions of users.
>> > We implement reCAPTCHA on our donation forms for security, and an invalid
>> > certificate warning means our nonprofit clients are losing donations because
>> > donors won’t enter credit card information on an unsecure page.

>> > We are in the process of updating all versions of our software, but it is
>> > unreasonable for us to upgrade thousands of clients “within the next couple
>> > days”, especially if we don’t even control the servers they’re running on.
>> > I would strongly encourage and appeal to you to extend the “rollback” for a
>> > period of 3-6 months (or longer) in order to give us a chance to properly
>> > fix, test, and update our products, and give our clients time to apply those
>> > updates.

>> > tjengine

>> > --
>> > 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.

>> >  --
>> > 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.

>> --
>> PJH

> --
> 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.

> Not even that late - it was announced June 30th 2010.

> <http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

> It's not as if it should be a complete surprise to anyone.

> If 9 months is insufficient time to roll out this sort of thing, I'm failing
> to see how a further "3-6 months" is going to help.

> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <adrian.god...@gmail.com>wrote:

> > AFAIK the change has been announced since late last year.

> > ---
> > Adrian Godong

> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

> > Hello,

> > This is an extremely painful change that I hope you will reconsider.  Our
> > software serves thousands of nonprofit organizations with millions of users.
> > We implement reCAPTCHA on our donation forms for security, and an invalid
> > certificate warning means our nonprofit clients are losing donations because
> > donors won’t enter credit card information on an unsecure page.

> > We are in the process of updating all versions of our software, but it is
> > unreasonable for us to upgrade thousands of clients “within the next couple
> > days”, especially if we don’t even control the servers they’re running on.
> > I would strongly encourage and appeal to you to extend the “rollback” for a
> > period of 3-6 months (or longer) in order to give us a chance to properly
> > fix, test, and update our products, and give our clients time to apply those
> > updates.

> > tjengine

> > --
> > 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.

> >  --
> > 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.

> --
> PJH- Hide quoted text -

> - Show quoted text -

On Wed, Apr 13, 2011 at 13:02, Adrian Godong <adrian.god...@gmail.com> wrote:
> Looks like v0.0.7 is updated way back in 2008. Might be easier to get
> the latest source, change the URL, and build it yourself.

> I don't think anyone created that library is still maintaining it.

> On Wed, Apr 13, 2011 at 12:58, TG <ashoktheg...@gmail.com> wrote:
>> Hi All

>> recaptcha4j-0.0.7.zip present at the location (http://code.google.com/
>> p/recaptcha4j/downloads/detail?name=recaptcha4j-0.0.7.jar&can=2&q=)
>> still contains the URLs of the following format like "http://
>> api.recaptcha.net", "https://api-secure.recaptcha.net", "http://api-
>> verify.recaptcha.net/verify".
>> Its still not updated.

>> Thanks
>> TG

>> On Apr 13, 3:31 pm, PJH <pauljherr...@gmail.com> wrote:
>>> Not even that late - it was announced June 30th 2010.

>>> <http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

>>> It's not as if it should be a complete surprise to anyone.

>>> If 9 months is insufficient time to roll out this sort of thing, I'm failing
>>> to see how a further "3-6 months" is going to help.

>>> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <adrian.god...@gmail.com>wrote:

>>> > AFAIK the change has been announced since late last year.

>>> > ---
>>> > Adrian Godong

>>> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

>>> > Hello,

>>> > This is an extremely painful change that I hope you will reconsider.  Our
>>> > software serves thousands of nonprofit organizations with millions of users.
>>> > We implement reCAPTCHA on our donation forms for security, and an invalid
>>> > certificate warning means our nonprofit clients are losing donations because
>>> > donors won’t enter credit card information on an unsecure page.

>>> > We are in the process of updating all versions of our software, but it is
>>> > unreasonable for us to upgrade thousands of clients “within the next couple
>>> > days”, especially if we don’t even control the servers they’re running on.
>>> > I would strongly encourage and appeal to you to extend the “rollback” for a
>>> > period of 3-6 months (or longer) in order to give us a chance to properly
>>> > fix, test, and update our products, and give our clients time to apply those
>>> > updates.

>>> > tjengine

>>> > --
>>> > 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.

>>> >  --
>>> > 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.

>>> --
>>> PJH

>> --
>> 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.

> --
> Adrian Godong
> adrian.god...@gmail.com

> Or use v.0.0.8 instead SOL

> On Wed, Apr 13, 2011 at 13:02, Adrian Godong <adrian.god...@gmail.com> wrote:
> > Looks like v0.0.7 is updated way back in 2008. Might be easier to get
> > the latest source, change the URL, and build it yourself.

> > I don't think anyone created that library is still maintaining it.

> > On Wed, Apr 13, 2011 at 12:58, TG <ashoktheg...@gmail.com> wrote:
> >> Hi All

> >> recaptcha4j-0.0.7.zip present at the location (http://code.google.com/
> >> p/recaptcha4j/downloads/detail?name=recaptcha4j-0.0.7.jar&can=2&q=)
> >> still contains the URLs of the following format like "http://
> >> api.recaptcha.net", "https://api-secure.recaptcha.net", "http://api-
> >> verify.recaptcha.net/verify".
> >> Its still not updated.

> >> Thanks
> >> TG

> >> On Apr 13, 3:31 pm, PJH <pauljherr...@gmail.com> wrote:
> >>> Not even that late - it was announced June 30th 2010.

> >>> <http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

> >>> It's not as if it should be a complete surprise to anyone.

> >>> If 9 months is insufficient time to roll out this sort of thing, I'm failing
> >>> to see how a further "3-6 months" is going to help.

> >>> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <adrian.god...@gmail.com>wrote:

> >>> > AFAIK the change has been announced since late last year.

> >>> > ---
> >>> > Adrian Godong

> >>> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

> >>> > Hello,

> >>> > This is an extremely painful change that I hope you will reconsider.  Our
> >>> > software serves thousands of nonprofit organizations with millions of users.
> >>> > We implement reCAPTCHA on our donation forms for security, and an invalid
> >>> > certificate warning means our nonprofit clients are losing donations because
> >>> > donors won’t enter credit card information on an unsecure page.

> >>> > We are in the process of updating all versions of our software, but it is
> >>> > unreasonable for us to upgrade thousands of clients “within the next couple
> >>> > days”, especially if we don’t even control the servers they’re running on.
> >>> > I would strongly encourage and appeal to you to extend the “rollback” for a
> >>> > period of 3-6 months (or longer) in order to give us a chance to properly
> >>> > fix, test, and update our products, and give our clients time to apply those
> >>> > updates.

> >>> > tjengine

> >>> > --
> >>> > 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.

> >>> >  --
> >>> > 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.

> >>> --
> >>> PJH

> >> --
> >> 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.

> > --
> > Adrian Godong
> > adrian.god...@gmail.com

> --
> Adrian Godong
> adrian.god...@gmail.com

> At last found the JAR here.......recaptcha4j-0.0.8.jar

> http://code.google.com/p/recaptcha4j/downloads/list

> -Sam

> On Apr 13, 4:03 pm, Adrian Godong <adrian.god...@gmail.com> wrote:

> > Or use v.0.0.8 instead SOL

> > On Wed, Apr 13, 2011 at 13:02, Adrian Godong <adrian.god...@gmail.com> wrote:
> > > Looks like v0.0.7 is updated way back in 2008. Might be easier to get
> > > the latest source, change the URL, and build it yourself.

> > > I don't think anyone created that library is still maintaining it.

> > > On Wed, Apr 13, 2011 at 12:58, TG <ashoktheg...@gmail.com> wrote:
> > >> Hi All

> > >> recaptcha4j-0.0.7.zip present at the location (http://code.google.com/
> > >> p/recaptcha4j/downloads/detail?name=recaptcha4j-0.0.7.jar&can=2&q=)
> > >> still contains the URLs of the following format like "http://
> > >> api.recaptcha.net", "https://api-secure.recaptcha.net", "http://api-
> > >> verify.recaptcha.net/verify".
> > >> Its still not updated.

> > >> Thanks
> > >> TG

> > >> On Apr 13, 3:31 pm, PJH <pauljherr...@gmail.com> wrote:
> > >>> Not even that late - it was announced June 30th 2010.

> > >>> <http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

> > >>> It's not as if it should be a complete surprise to anyone.

> > >>> If 9 months is insufficient time to roll out this sort of thing, I'm failing
> > >>> to see how a further "3-6 months" is going to help.

> > >>> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <adrian.god...@gmail.com>wrote:

> > >>> > AFAIK the change has been announced since late last year.

> > >>> > ---
> > >>> > Adrian Godong

> > >>> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

> > >>> > Hello,

> > >>> > This is an extremely painful change that I hope you will reconsider.  Our
> > >>> > software serves thousands of nonprofit organizations with millions of users.
> > >>> > We implement reCAPTCHA on our donation forms for security, and an invalid
> > >>> > certificate warning means our nonprofit clients are losing donations because
> > >>> > donors won’t enter credit card information on an unsecure page.

> > >>> > We are in the process of updating all versions of our software, but it is
> > >>> > unreasonable for us to upgrade thousands of clients “within the next couple
> > >>> > days”, especially if we don’t even control the servers they’re running on.
> > >>> > I would strongly encourage and appeal to you to extend the “rollback” for a
> > >>> > period of 3-6 months (or longer) in order to give us a chance to properly
> > >>> > fix, test, and update our products, and give our clients time to apply those
> > >>> > updates.

> > >>> > tjengine

> > >>> > --
> > >>> > 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.

> > >>> >  --
> > >>> > 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.

> > >>> --
> > >>> PJH

> > >> --
> > >> 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.

> > > --
> > > Adrian Godong
> > > adrian.god...@gmail.com

> > --
> > Adrian Godong
> > adrian.god...@gmail.com

On Wed, Apr 13, 2011 at 10:57 PM, Recapthaxx <sam.india...@gmail.com> wrote:
> Does the following URL also need to be changed ?

> api-verify.recaptcha.net

> If so, what would be the URL ?

> Ind

> On Apr 13, 4:08 pm, RecaptchaGoogleGroup <sambonig...@gmail.com>
> wrote:
> > At last found the JAR here.......recaptcha4j-0.0.8.jar

> > http://code.google.com/p/recaptcha4j/downloads/list

> > -Sam

> > On Apr 13, 4:03 pm, Adrian Godong <adrian.god...@gmail.com> wrote:

> > > Or use v.0.0.8 instead SOL

> > > On Wed, Apr 13, 2011 at 13:02, Adrian Godong <adrian.god...@gmail.com>
> wrote:
> > > > Looks like v0.0.7 is updated way back in 2008. Might be easier to get
> > > > the latest source, change the URL, and build it yourself.

> > > > I don't think anyone created that library is still maintaining it.

> > > > On Wed, Apr 13, 2011 at 12:58, TG <ashoktheg...@gmail.com> wrote:
> > > >> Hi All

> > > >> recaptcha4j-0.0.7.zip present at the location (
> http://code.google.com/
> > > >> p/recaptcha4j/downloads/detail?name=recaptcha4j-0.0.7.jar&can=2&q=)
> > > >> still contains the URLs of the following format like "http://
> > > >> api.recaptcha.net", "https://api-secure.recaptcha.net", "
> http://api-
> > > >> verify.recaptcha.net/verify".
> > > >> Its still not updated.

> > > >> Thanks
> > > >> TG

> > > >> On Apr 13, 3:31 pm, PJH <pauljherr...@gmail.com> wrote:
> > > >>> Not even that late - it was announced June 30th 2010.

> > > >>> <
> http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

> > > >>> It's not as if it should be a complete surprise to anyone.

> > > >>> If 9 months is insufficient time to roll out this sort of thing,
> I'm failing
> > > >>> to see how a further "3-6 months" is going to help.

> > > >>> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <
> adrian.god...@gmail.com>wrote:

> > > >>> > AFAIK the change has been announced since late last year.

> > > >>> > ---
> > > >>> > Adrian Godong

> > > >>> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

> > > >>> > Hello,

> > > >>> > This is an extremely painful change that I hope you will
> reconsider.  Our
> > > >>> > software serves thousands of nonprofit organizations with
> millions of users.
> > > >>> > We implement reCAPTCHA on our donation forms for security, and an
> invalid
> > > >>> > certificate warning means our nonprofit clients are losing
> donations because
> > > >>> > donors won’t enter credit card information on an unsecure page.

> > > >>> > We are in the process of updating all versions of our software,
> but it is
> > > >>> > unreasonable for us to upgrade thousands of clients “within the
> next couple
> > > >>> > days”, especially if we don’t even control the servers they’re
> running on.
> > > >>> > I would strongly encourage and appeal to you to extend the
> “rollback” for a
> > > >>> > period of 3-6 months (or longer) in order to give us a chance to
> properly
> > > >>> > fix, test, and update our products, and give our clients time to
> apply those
> > > >>> > updates.

> > > >>> > tjengine

> > > >>> > --
> > > >>> > 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.

> > > >>> >  --
> > > >>> > 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.

> > > >>> --
> > > >>> PJH

> > > >> --
> > > >> 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.

> > > > --
> > > > Adrian Godong
> > > > adrian.god...@gmail.com

> > > --
> > > Adrian Godong
> > > adrian.god...@gmail.com

> --
> 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.

> On Wed, Apr 13, 2011 at 10:57 PM, Recapthaxx <sam.india...@gmail.com> wrote:
> > Does the following URL also need to be changed ?

> > api-verify.recaptcha.net

> Yes.

> > If so, what would be the URL ?

> From the URL I provided<http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...>for
> the message from last June:

> api-verify.recaptcha.net/verify is nowwww.google.com/recaptcha/api/verify

> Thanks,

> > Ind

> > On Apr 13, 4:08 pm, RecaptchaGoogleGroup <sambonig...@gmail.com>
> > wrote:
> > > At last found the JAR here.......recaptcha4j-0.0.8.jar

> > >http://code.google.com/p/recaptcha4j/downloads/list

> > > -Sam

> > > On Apr 13, 4:03 pm, Adrian Godong <adrian.god...@gmail.com> wrote:

> > > > Or use v.0.0.8 instead SOL

> > > > On Wed, Apr 13, 2011 at 13:02, Adrian Godong <adrian.god...@gmail.com>
> > wrote:
> > > > > Looks like v0.0.7 is updated way back in 2008. Might be easier to get
> > > > > the latest source, change the URL, and build it yourself.

> > > > > I don't think anyone created that library is still maintaining it.

> > > > > On Wed, Apr 13, 2011 at 12:58, TG <ashoktheg...@gmail.com> wrote:
> > > > >> Hi All

> > > > >> recaptcha4j-0.0.7.zip present at the location (
> >http://code.google.com/
> > > > >> p/recaptcha4j/downloads/detail?name=recaptcha4j-0.0.7.jar&can=2&q=)
> > > > >> still contains the URLs of the following format like "http://
> > > > >> api.recaptcha.net", "https://api-secure.recaptcha.net", "
> >http://api-
> > > > >> verify.recaptcha.net/verify".
> > > > >> Its still not updated.

> > > > >> Thanks
> > > > >> TG

> > > > >> On Apr 13, 3:31 pm, PJH <pauljherr...@gmail.com> wrote:
> > > > >>> Not even that late - it was announced June 30th 2010.

> > > > >>> <
> >http://groups.google.com/group/recaptcha/browse_thread/thread/7a4839d...

> > > > >>> It's not as if it should be a complete surprise to anyone.

> > > > >>> If 9 months is insufficient time to roll out this sort of thing,
> > I'm failing
> > > > >>> to see how a further "3-6 months" is going to help.

> > > > >>> On Wed, Apr 13, 2011 at 7:26 PM, Adrian Godong <
> > adrian.god...@gmail.com>wrote:

> > > > >>> > AFAIK the change has been announced since late last year.

> > > > >>> > ---
> > > > >>> > Adrian Godong

> > > > >>> > On Apr 13, 2011, at 12:19, tjengine <tjande...@gmail.com> wrote:

> > > > >>> > Hello,

> > > > >>> > This is an extremely painful change that I hope you will
> > reconsider.  Our
> > > > >>> > software serves thousands of nonprofit organizations with
> > millions of users.
> > > > >>> > We implement reCAPTCHA on our donation forms for security, and an
> > invalid
> > > > >>> > certificate warning means our nonprofit clients are losing
> > donations because
> > > > >>> > donors won’t enter credit card information on an unsecure page.

> > > > >>> > We are in the process of updating all versions of our software,
> > but it is
> > > > >>> > unreasonable for us to upgrade thousands of clients “within the
> > next couple
> > > > >>> > days”, especially if we don’t even control the servers they’re
> > running on.
> > > > >>> > I would strongly encourage and appeal to you to extend the
> > “rollback” for a
> > > > >>> > period of 3-6 months (or longer) in order to give us a chance to
> > properly
> > > > >>> > fix, test, and update our products, and give our clients time to
> > apply those
> > > > >>> > updates.

> > > > >>> > tjengine

> > > > >>> > --
> > > > >>> > 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.

> > > > >>> >  --
> > > > >>> > 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.

> > > > >>> --
> > > > >>> PJH

> > > > >> --
> > > > >> 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.

> > > > > --
> > > > > Adrian Godong
> > > > > adrian.god...@gmail.com

> > > > --
> > > > Adrian Godong
> > > > adrian.god...@gmail.com

> > --
> > 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.

> --
> PJH

> Just externalize the required code, something like this...

> Replace

> ReCaptcha captcha =
> ReCaptchaFactory.newSecureReCaptcha(recapConfig.getPublickey(),
> recapConfig.getPrivatekey(), false);

> with

> ReCaptchaImpl recaptcha = new ReCaptchaImpl();
> recaptcha.setIncludeNoscript(false);
> recaptcha.setPrivateKey(recapConfig.getPrivatekey());
> recaptcha.setPublicKey(recapConfig.getPublickey());
> recaptcha.setRecaptchaServer("https://www.google.com/recaptcha/api");

> or pick code from

> http://code.google.com/p/recaptcha/downloads/detail?name=recaptcha4j-...

> and create your own jar, replacing the HTTPS URL.

> -Sam

> On Apr 13, 2:10 pm, Surya Metla <surya.me...@gmail.com> wrote:

> > Hi All

> > Is there a new java jar file available to download. The version i have
> > recaptcha4j-0.0.7.zip still pointed to old URL.

> > Thanks In advance

> > Suri

> > On Apr 13, 1:48 pm, reCAPTCHA Support <supp...@recaptcha.net> wrote:

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

> > > To clarify Adrian's comment,

> > > The .NET control from last December:http://code.google.com/p/recaptcha/downloads/detail?name=recaptcha-do...
> > > already used the new URLs. If you are use version 1.0.5, it should work.

> > > Colin