🚀 go-pugleaf

Hello Dave,

I am not sure why the transport thinks that the certificate is invalid but
there's an option that might be helpful: The THTTPReqResp component has a
property 'InvokeOptions' that expose a 'soIgnoreInvalidCert' setting. When
enabled, the component will set the INTERNET_FLAG_xxxx flags to ignore
expired/invalid dates and disable the host name check performed by WinInet.

Maybe the certificate is assigned to a different host than how you're
accessing the server (during our recent switch from 'borland' to 'codegear'
my tests with Borland webservices generated a similar error because the
certificate is assigned to 'borland', not the 'codegear.com' I'm now using).

Let me know if the above does not help and we'll investigate some more.

Cheers,

Bruneau.

PS: As a client you get to that property via
THTTPRIO->HTTPWebMode->InvokeOptions.