Question:
After a yearly certificate update form ourprovider the Chilkat.Http suddely stopped working
producing this error:
VerboseLogging: 0
url: https://inquiry.creditandcollection.nl/api/companies?country=NL&term=timerfruit
httpRequestStr:
a_quickReq:
quickHttpRequest:
httpVerb: GET
url: https://inquiry.creditandcollection.nl/api/companies?country=NL&term=xxx
openHttpConnection:Opening connection directly to HTTP server.
httpHostname: inquiry.creditandcollection.nl
httpPort: 443
ssl: 1
socket2Connect:
connect2:
connectImplicitSsl:
clientHandshake:
clientHandshake2:
readHandshakeMessages:
processAlert:
TlsAlert:
level: fatal
descrip: handshake failure
--TlsAlert
Closing connection in response to fatal SSL/TLS alert.
--processAlert
Aborting handshake because of fatal alert.
--readHandshakeMessages
--clientHandshake2
--clientHandshake Client handshake failed. (3)
--connectImplicitSsl
ConnectFailReason: 0
--connect2
--socket2Connect
--openHttpConnection
--quickHttpRequest
--a_quickReq
--httpRequestStr Failed.
--QuickGetStr
I already did some research by testing this 'renewed' cert using: https://www.ssllabs.com/ssltest/index.html httpHostname: inquiry.creditandcollection.nl
and I found out that it could be a issue when the server has 2 paths to the Cert
Is there a known issue with the Chilkat.Http sslrequest and having 2 paths ? thanks for looking at this issue ...
Hans