🚀 go-pugleaf

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

> It comes a first part, that contains the header and an hexa that say
> the number of bytes to read. Then on the next loop, I receive a new
> chunk with a new hexa that says the length of the new chunk, a
> third time this occour and on the fourth, the signal that the send
of
> chunked data ends is present "0\r\n\r\n". So I quit the loop because
> there not more data to read...

That is how chunked transfers work, but that is not how your earlier
code was actually reading chunked data.  You were not reading the
chunked sizes at all.  You were reading the incoming data in arbitrary
byte sizes into a buffer without any care whatsoever to the actual
content of the transfer, and then trying to verify the last chunk
only.  A proper transfer should be performing the following sequence
instead:

    send the request
    read a single line
    verify the response code in the line
    loop
        read a line
        if line is empty then break
        store the line into a header list
    end
    if list contains 'Transfer-Encoding: chunked' header then
    begin
        loop
            read a line
            extract chunk size from the line
            if chunk size is 0 then break
            read number of bytes specified
            store bytes into buffer
            read an empty line
        end
        read an empty line
    end
    else if list contains 'Content-Length' header then
    begin
        read number of bytes specified
        store bytes into buffer
    end
    else
    begin
        loop
            read as many bytes as are currently available
            if disconnected then break
            store bytes into buffer
        end
    end

> And what I must to do?

See above.


Gambit