🚀 go-pugleaf

"Ted Tripp" <ttripp@rankexec.com> wrote in message
news:41b15c54$1@newsgroups.borland.com...

> The resulting page stops at "AMPLIFIES THE TERROR WITH
> DOOM3: RESURRECTION OF EVIL_ Santa Monica, CA " without
> completing the content and it appears that somewhere after the CA
> there is a special character that I am guessing IdHTTP is interpreting as
> an end-of-content marker.  This occurs rarely, but is a real show stopper
> for some of the things I am trying to do.

There is no such end-of-content character in the HTTP protocol, let alone
one that makes TIdHTTP stop reading the socket for data.  There are only
three things that make TIdHTTP stop reading:

1) There is a "Content-Length" header present, so TIdHTTP reads until the
full amount specified has been read

2) There is no "Content-Length" header present, but there is a
"Transfer-Encoding" header of "chucked" present, so the socket is read in
multiple blocks until no more blocks are transmitted.

3) there is no "Content-Length" or "chunked" headers present, so TIdHTTP
reads the socket until a reading timeout between 2-4 seconds occurs, meaning
no more data has been transmitted by the server.


Gambit