I used another machine and I no longer get the socket error (apparently
networking is getting creative again with our dns), but now it's a read
time-out error (almost immediately after calling Get).
Dang, it shouldn't be this hard.
function TdmUSPSCustomsFormCP72.GetResponse(const URL, XML: String): String;
var
WebURL: string; {for debugging}
URI :TIdURI;
begin
Result := '';
URI := TIdURI.Create();
try
WebURL := URL + '&XML=' + URI.ParamsEncode(XML);
{debugging code snipped}
try
Result := IdUSPSCustomsServer.Get(WebURL);
{debugging code snipped}
except
on E: Exception do
begin
Result := E.Message;
end;
end;
finally { wrap up }
URI.Free();
end; { try/finally }
end;
"Kevin Frevert" <kevin@workdrinkingicewater> wrote in message
news:475570a4$1@newsgroups.borland.com...
> After upgrading from D6 (Indy 9) to Delphi 2007 (default Indy 10
> components), and attempting to send/receive (xml) data from a secured site
> (https) I received the error/exception 'IOHandler value is not valid'.
>
> OK, I searched around and find out I need a 'Handler' component, which I
> did not need before (code has gone unchanged since 2004)
>
> I try out TIdServerIOHandlerSSLOpenSSL (no changes to the component) and
> when I attempt again, I receive the error/exception 'Socket Error # 11004'
>
> I went as far as downloading the OpenSSL dlls and placing them in the
> application's directory, same error.
>
> A bit frustrating to say the least.
>
> Is there a workaround? What's the trick in using the TidHttp component
> against https sites? Has Indy feature-creeped itself into obscurity and
> it's time to use something else?
>
> Thanks for any info,
> krf
