-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ios 9.x - ipv6 Test not work.. (CURLE_COULDNT_CONNECT) #594
Comments
Are you running a program that works fine otherwise on other platforms (like native mac) ? CURLE_COULDNT_CONNECT means libcurl failed to establish a TCP connection to the remote host (and port). Are you sure you're supposed to be able to without using a proxy or any other similar means? Can you telnet to that host + port from the same machine that curl fails to work on? Can you generate a full VERBOSE-enabled log for when you do this and show us? I don't think we have many iPhone users among or developers so I think you're left a bit on your own to further debug this. But me knowingly, it should just work fine on iOS as well. Have you gotten this to work with any other libcurl version? |
(1) normal network is no problem (live ios (iphone,ipad..) project) (3) version
|
if ipv4 works and ipv6 doesn't, that sounds more like an OS issue then anything else to me. libcurl really doesn't do much difference between IP versions and CURLE_COULDNT_CONNECT means that connect() returned a failure. What else can we do? |
thanks, your answer. |
(1) how to check ipv6 able?
(2) if ipv6 check is “curl_version_info->features & CURL_VERSION_IPV6” , (3) hot to set ipv6 able ?
(etc) curl_version_info->features value (ipv6 not work state)
(my code) res = curl_easy_perform(curl); |
The You need a libcurl built to support IPv6 in order to use IPv6. |
A libcurl without IPv6 support cannot speak IPv6. |
(1) ios device is not VERBOSE log. (simulator is log has) (2) simulator log (normal case) * Trying 80.67.6.50...
* Connected to curl.haxx.se (80.67.6.50) port 80 (#0)
> POST / HTTP/1.1
Host: curl.haxx.se
Accept: */*
Content-Type: text/html
Content-Length: 1388
Expect: 100-continue
< HTTP/1.1 100 Continue
< HTTP/1.1 200 OK
< Date: Tue, 12 Jan 2016 01:25:45 GMT
< Server: Apache
< Upgrade: h2c
< Connection: Upgrade
< Last-Modified: Mon, 11 Jan 2016 03:05:02 GMT
< ETag: "bda-5290634075674"
< Accept-Ranges: bytes
< Content-Length: 3034
< Vary: Accept-Encoding
< Content-Type: text/html
<
* Connection #0 to host curl.haxx.se left intact |
But that "normal case" shows it only using IPv4... An IPv6 capable curl would be more likely to say this:
|
(1) yes, "normal case" is using IPv4 (ios simulator)
|
When it says 'no', load the config.log file and search for the ipv6 test and you'll see what it tried to do and what failed. I think the problem is that when you cross-compile, that test doesn't really work. I would probably recommend you to manually edit |
I will actually switch the default for that for the next curl version. |
The configure test uses AC_TRY_RUN to figure out if an ipv6 socket works, and testing like that doesn't work for cross-compiles. These days IPv6 support is widespread so a blind guess is probably more likely to be 'yes' than 'no' now. Further: anyone who cross-compiles can use configure's --disable-ipv6 to explicitly disable IPv6 and that also works for cross-compiles. Made happen after discussions in issue #594
thanks, your answer. |
@masteage Is you app approved after change? I use https://github.com/sinofool/build-libcurl-ios to build curl with openssl, it can pass the DNS64/NAT64 local settings. But it's still rejected on Apple review ipv6 environment. |
@flyingsky Is Apple review still rejected? |
Under IPV6 environment, curl returns ok while running on simulators, but curl returns error while running on real iPhone device.I added the following code in my program to check IPV6 features: |
That feature is set at built time, so if you build libcurl with IPv6 support it will always show that bit in features. Also please don't piggyback on this issue. If you have libcurl questions ask them on the mailing list, or if you have a bug you can file it as a separate issue. I'm 99% sure that's not a bug though, very likely you are running some different version of libcurl not built with IPv6 support. |
setting
error
state
question
The text was updated successfully, but these errors were encountered: