IPv6 link to Recapcha API times out

[Justin]

As of June 6th, 2012, I am having an issue resolving the IPv6 version
of http://www.google.com/recaptcha/api/verify

Here is a Curl -V command ran from the web server:

curl -v http://www.google.com/recaptcha/api/verify
* About to connect() to www.google.com port 80 (#0)
* Trying 2607:f8b0:400f:801::1010... Connection timed out
* Trying 74.125.225.212... connected
* Connected to www.google.com (74.125.225.212) port 80 (#0)
> GET /recaptcha/api/verify HTTP/1.1
> User-Agent: curl/7.21.0 (i486-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.15 libssh2/1.2.6
> Host: www.google.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Cache-Control: no-cache, no-store, max-age=0, must-revalidate
< Pragma: no-cache
< Expires: Fri, 01 Jan 1990 00:00:00 GMT
< Date: Thu, 14 Jun 2012 21:28:20 GMT
< Content-Type: text/plain
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< Server: GSE
< Transfer-Encoding: chunked
<
false
* Connection #0 to host www.google.com left intact
* Closing connection #0


It stalled out for about 20 seconds trying the IPv6 address for Google
before it failed back to IPv4 which went right through. Since the
default timeout period of the Recaptcha script is set to 10 seconds
the web pages ends up stalling out and throwing a "Could not open
socket" error as stated in the recaptchalib.php file. with the timeout
period set to 30 seconds it is a quick work around for the issue. But
it is taking an extremely long time for the forms to complete their
process.

Please let me know if you have any questions.

[Justin]

Anyone have any ideas in regards to this issue?

[Dom Sekotill]

Are you still encountering this problem? I have no issue connecting via
IPv6 at the moment, in which case it may be a misconfiguration on your
machine and/or network. Can you connect to other services through IPv6?
For instance what does 'curl -v www.facebook.com' report? What is the
output of 'ifconfig'?

Dom

[froit]

Imgur-captcha works again as of this morning.

Another responder suggests it may have been an IPv6-issue.

I don't know what to say upon that.

Grt

Froit

--
You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.
To view this discussion on the web visit https://groups.google.com/d/msg/recaptcha/-/0DsZKfKp9XQJ.
To post to this group, send email to reca...@googlegroups.com.
To unsubscribe from this group, send email to recaptcha+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/recaptcha?hl=en.

Greetings,

Froit

in...@froit.nl

[froit]

I don't know how to use that script, bur as of this morning everything seems to be hurly-girly again.
So maybe iy was IPv6-relayed in my provider?
Would not surprise me in Mongolia...

Gty
Froit

Op 28 jun 2012, om do28-06-201222:02 heeft Dom Sekotill het volgende geschreven:

> Are you still encountering this problem? I have no issue connecting via IPv6 at the moment, in which case it may be a misconfiguration on your machine and/or network. Can you connect to other services through IPv6? For instance what does 'curl -v www.facebook.com' report? What is the output of 'ifconfig'?
>
> Dom
>

> --
> You received this message because you are subscribed to the Google Groups "reCAPTCHA" group.

[Justin]

This is fixed.

We found an issue with the way the IPv6 was routed out. It got missed on the first go around.

Thank you for the responses! 

On Tuesday, June 19, 2012 6:25:15 PM UTC-5, Justin wrote: