"Steve" <no.spam@onbox.com> wrote in message
news:4536ad82$1@newsgroups.borland.com...
> what could be the reason that the Indy HTTP Component
> (I've tried all builds 7,8,9,10x) with
>
> IdHTTP1.Get(MyUrl, MyMemoryStream);
>
> causes an exception
> #10057 (WSAENOTCONN)
Read the description for the error again. It tells you exactly why it is
occuring:
"A request to send or receive data was disallowed because the socket is
not connected..."
That is an API error, not an Indy error. Indy is trying to access a socket
that is not connected at the API layer. Why that is happening, I cannot
answer that without more details about what you are trying to download in
the first place. For all I know, the HTTP server is at fault, sending a
faulty reply to TIdHTTP that causes it to try to read more data than is
actually available.
Gambit
