[prev in list] [next in list] [prev in thread] [next in thread] 

List:       httpclient-commons-dev
Subject:    Re: Why is Part Content-Length Missing?
From:       Ortwin_Glück <odi () odi ! ch>
Date:       2006-01-19 18:38:33
Message-ID: 43CFDCA9.8070603 () odi ! ch
[Download RAW message or body]

Aden,

It's correct that multipart MIME is unsafe in that respect. On the other 
hand it allows to stream data whose size is not known beforehand. 
Unfortunately HttpClient's multipart implementation does not allow 
adding of custom headers easily. You may exchange it with a different 
implementation however.

Ortwin Glück

S. Aden wrote:
> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]