🚀 go-pugleaf

"Eduardo Jauch" <eduardo.jauch@gmail.com> wrote in message
news:45e24baa@newsgroups.borland.com...

> one of the recv return 0 bytes

That means that the other party has closed the connection gracefully.

> i'm not setting the socket to nonbloking and the connection does
> not time out by server not responding nor something like that.

recv does not return 0 in non-blocking mode when a timeout occurs.  It
returns SOCKET_ERROR (-1) and then WSAGetLastError() returns
WSAETIMEOUT.

> I'm using the recv to return only the HEAD (not using GET).

You are probably not taking into account that the server will likely
close the connection after sending its reply to any command.  That is
the default behavior for HTTP 1.0 requests.  The connection is only
left open when a keep-alive is negotiated between the client and the
server as part of the command/response exchange.  I'm guessing that
you are not reading the HTTP protocol documentation carefully enough,
as this is covered.

> When i use WSAGetLastError, always return code 6
> I search on help but not find any error code 6 returned by
> WSAGetLastError...

WSAGetLastError() is only meaningful when a real error occurs.  recv()
returning 0 is not an error condition.


Gambit