On May 16, 2009, at 8:38 PM, Antony Blakey wrote:
On 16/05/2009, at 8:45 PM, Adam Kocoloski wrote:
Hi Antony, thank you! I encountered this "one more byte" problem
once before, but it wasn't 100% reproducible, so I wasn't really
comfortable checking in a workaround. I've basically been waiting
to see if it would ever show up for anyone else :-/
I think we should commit this change, but I'd still like to confirm
that the attachment on the target is not corrupted by the chunk
processing issue (i.e. the last chunk starts with a \r or something
like that). Or even better, fix the chunk processing issue.
Given my results, will you commit that fix?
Yes, I committed it now. Thanks, Adam