uh, hate to bring up a no-brainer, but just out of curiosity, is the Content-length request header accurate for the encoded payload *after* it's encoded? just on the off chance that libapreq2 is stricter than libapreq1, an error like "end of file reached" would occur if there was extraneous data after the buffer of Content-Length size was filled. i'd make sure to double, nay, triple-check that value in the vb.
On Mon, Jun 20, 2005 at 09:07:57PM -0400, Joe Schaefer wrote: > "D. Hageman" <dhageman@dracken.com> writes: > > > ggRIAAAAASUVORK5CYII=\r\n--AaB03x-- > ^^ > Missing an \r\n there I think. > > > -- > Joe Schaefer >
