Archived Forum Post

Index of archived forum posts

Question:

QuickGetStr(URL) fails with https address

Apr 13 '16 at 12:00

When i call https://www.moebelgarten-shop.com/, I get this error.
Some time ago without SSL the same routine worked fine. Any ideas?

  QuickGetStr:
    DllDate: Jul 31 2014
    ChilkatVersion: 9.5.0.43
    UnlockPrefix: MARKUSHttp
    Username: UMW10:um
    Architecture: Little Endian; 32-bit
    Language: .NET 4.0
    VerboseLogging: 0
    httpRequestStr:
      a_quickReq:
        quickHttpRequest:
          httpVerb: GET
          url: https://www.moebelgarten-shop.com/
          openHttpConnection:
            Opening connection directly to HTTP server.
            httpHostname: www.moebelgarten-shop.de
            httpPort: 443
            ssl: 1
            socket2Connect:
              connect2:
                connectImplicitSsl:
                  clientHandshake:
                    clientHandshake2:
                      processHandshakeRecord:
                        processHandshakeMessage:
                          processServerHello:
                            HelloExtension: renegotiation_info
                            HelloExtensionLen: 1
                            HelloExtension: status_request
                            HelloExtensionLen: 0
                          --processServerHello
                        --processHandshakeMessage
                      --processHandshakeRecord
                      Did not receive the expected ChangeCipherSpec.
                    --clientHandshake2
                  --clientHandshake
                  Client handshake failed. (3)
                --connectImplicitSsl
                ConnectFailReason: 0
              --connect2
            --socket2Connect
            ConnectFailReason: 0
            connectElapsedMs: 141
          --openHttpConnection
        --quickHttpRequest
      --a_quickReq
    --httpRequestStr
    Failed.
  --QuickGetStr
--ChilkatLog

---

Answer

I tested with the latest version of Chilkat, and it works fine.

---

Answer

Yes, updated dll works fine! Thank you.