hmm, interesting. haven't seen this specific bug before.
probably httpchannel truncates the content-length to 32bit, and stops reading from the socket after having read the truncated number of bytes?
hmm, interesting. haven't seen this specific bug before.
probably httpchannel truncates the content-length to 32bit, and stops reading
from the socket after having read the truncated number of bytes?