I've noticed this recently too - I think it has to do with recent Windows updates and the WinInet libraries where some requests seem to indicate failure of hte certificate.

As far as I know there's no way to work around this with the SOAP Toolkit because the HTTP client is pretty much closed.

You can try using wwSoap (www.west-wind.com/wwsoap.asp) which allows configuration of the HTTP client. There are flags taht can turn off the Cert validation restrictions ( via several WinInet service flags ).

+++ Rick ---


>Hi,
>
>I need create client for this webservice:
>
>https://200.214.130.41:9443/farmaciahomologa/services/ServicoSolicitacaoWS?wsdl
>
>But in VFP return ERROR: Certificate no valid.
>
>Yes, no valid and this no registrer in vfp. Others languagens .NET, java e delphi change properties and run.
>
>Who to do register this in my project?
>
>tanks.