some cases (when TCP/IP splits the client request in several packets) it
only reads the first packet. Therefore, not the whole request string is
read.
We tried to solve that by calling ReadClient within a loop until the
whole Content-lenth amount of bytes is read. However, if the
content-length is garbage, this causes the plugin to wait indefinitely.
Is there a timeout that can be called with the ReadClient?
Has anybody an idea what to do?
Thanks,
Robert
I had encountered the same trouble with ReadClient and had submitted a bug
to Netscape a few moths ago, I do not know what is the result.
My own investigation's result was that content-lenght is always correct but
depending on how the browser partitions the data into packets ReadClient may
or may not work.
The only case that seems to always work is calling ReadClient only once and
to read the whole input from the browser, i.e. reading content-lenght bytes
at one call.
This was not a good solution for reading multi-part form data input, you
usually want to read one part at a time. OTH, multi-part form data request
seems to always work when the browser is IE, regardless of how you call
ReadClient. That is because of the specific way IE partitions the request
header and request data into packets.
If you come-up with any other informations I really would like to know it.
Thanks,
Ahmet Feyz Pirimoglu
Robert Engel <ren...@imageminds.com> wrote in message
news:37B9A0D2...@imageminds.com...