Author Topic: CkHttp not resolving IPv6  (Read 731 times)

lavoiekeven

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
CkHttp not resolving IPv6
« on: November 06, 2017, 02:31:05 PM »
Hi,
I'have a site that is only available with IPv6. I'm trying to do a transaction using the hostname and CKHttp but it fails.

With ping, the resolution works:
Code: [Select]
Envoi d’une requête 'ping' sur SITEAWIN2012 [fe80::b89b:f65a:a017:ed0f%17] avec 32 octets de données :
Réponse de fe80::b89b:f65a:a017:ed0f%17 : temps=22 ms
Réponse de fe80::b89b:f65a:a017:ed0f%17 : temps=21 ms
Réponse de fe80::b89b:f65a:a017:ed0f%17 : temps=23 ms
Réponse de fe80::b89b:f65a:a017:ed0f%17 : temps=25 ms

I'm also able to connect with telnet on the port 80.

but with CkHttp it returns :
Code: [Select]
ChilkatLog:
  SynchronousRequest:
    DllDate: Nov 25 2016
    ChilkatVersion: 9.5.0.65
    UnlockPrefix: IMAGEMHttp
    Architecture: Little Endian; 64-bit
    Language: Visual C++ 10.0 / x64
    VerboseLogging: 0
    domain: SITEAWIN2012
    port: 80
    ssl: 0
    originallySetFromUrl: http://SITEAWIN2012:80/PSlicence/api/v1/authentication
    httpRequest:
      httpVersion: 1.1
      verb: POST
      path: /PSlicence/api/v1/authentication
      contentType: application/x-www-form-urlencoded
      charset: windows-1252
      sendCharset: 0
      mimeHeader:
      requestParams:
        requestItem:
          name: action
          value: login
        --requestItem
        requestItem:
          name: source
          value: PSSCRIPT
        --requestItem
        requestItem:
          name: computer
          value: KEVEN-PC
        --requestItem
        requestItem:
          name: username
          value: KEVEN
        --requestItem
        requestItem:
          name: password
          value: 0
        --requestItem
      --requestParams
    --httpRequest
    fullRequest:
      a_synchronousRequest:
        generateRequestHeader:
          httpRequestGenStartLine:
            genStartLine:
              startLine: POST /PSlicence/api/v1/authentication HTTP/1.1
            --genStartLine
          --httpRequestGenStartLine
          addCookies:
            Not auto-adding cookies.
            sendCookies: 1
            cookieDir:
          --addCookies
        --generateRequestHeader
        fullHttpRequest:
          domain: siteawin2012
          port: 80
          ssl: 0
          openHttpConnection:
            Opening connection directly to HTTP server.
            httpHostname: siteawin2012
            httpPort: 80
            ssl: 0
            socket2Connect:
              connect2:
                connectSocket:
                  connect_ipv6_or_ipv4:
                    timeout waiting for connect to complete
                    numSec: 20
                    numMicroSec: 0
                    failedWaitToConnect: Socket operation timeout.
                  --connect_ipv6_or_ipv4
                --connectSocket
                ConnectFailReason: Timeout
                A few possible causes for a connection timeout are:
                - The remote host is not reachable (perhaps a firewall is blocking the connection on the remote end).
                - Your ISP is blocking the outbound connection (this is common for SMTP port 25).
                - If your timeout is too short, then maybe the server is just too slow to accept the connection.
              --connect2
            --socket2Connect
            connect: Socket operation timeout.
          --openHttpConnection
        --fullHttpRequest
        success: 0
      --a_synchronousRequest
      success: 0
    --fullRequest
    totalTime: Elapsed time: 20406 millisec
    Failed.
  --SynchronousRequest
--ChilkatLog