My problem is that while it is highly unlikely that the boundary string will appear in the content itself there is no guarantee that it won't unless you Base64 encode the content you're sending (dash will never appear in Base64 encoded content). What I really wanted to do is to add another level of assurance if I choose not to encode the content by adding a Content-Length header attribute for each part so that I am not relying on only the boundary string to tell me when the next part begins.
-Aden On 19 Jan 2006 09:39:52 +0100, Guillaume Cottenceau <[EMAIL PROTECTED]> wrote: > "S. Aden" <aden.list 'at' gmail.com> writes: > > > I am trying to post several files to a server using HTTPClient 3.0 and > > would like to include the length of each file part in the part header. > > (after reading Oleg responses) Maybe it would help us if you > would explain what problem you are trying to solve with this > approach? > > -- > Guillaume Cottenceau > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
