I’m using your latest version of curl to connect to ssl url - the certificate authentication works not on all defined hosts
The response on the command looks like this
subject: C=AT; ST=Vienna; L=Vienna; O=xxxxxxxxxxxx GmbH; OU=Web Services; CN=xxx-web.r-services.at
start date: 2013-06-14 08:29:06 GMT
expire date: 2018-06-13 08:29:06 GMT
with other hostname it works. I think the problem seems not to be the certificate but something with ebcdic ascii conversion. Any suggestion how to fix that.
I am experiencing the exact same scenario with curl. Can you please advise how or if you resolved your issue.
Thanks in advance.
We suggest that you retry the command, supplying the additional argument -k. This argument disables some of the checks, and might allow it to work.
We would like to replicate this problem here. Can you suggest a public URL that might demonstrate this problem?
We are not sure whether IDN support is required for this to work, unfortunately we do not currently have a version of curl that contains support for IDN.
Yes you are right - specifying the -k option is working but it is unsecure.
Unfortunately all the url we are using not for public use. If you will need
any documentation material I can create it for you.
I do not know if really IDN might be the problem - because on the working
and the not working command the verbose output says
IDN support not present, can’t parse Unicode domains
thank you for your assistance
My understanding is that it is a feature of curl and that you need to use –k or fix your certificate.
xxx-web.r-services.at in fact does not match hnb-web.r-services.at
sorry - I changed it to xxx - the url in the certificate matches to
Fundamental problem here is that our cURL port does not support ASCII. We are planning to release another port of cURL with ASCII support but it will not be for another few months per our current schedule.
Yes - I think that points in the right direction.
Can you provide me a testing version of the port as soon as you’ve got it.