james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: Parsing header bug?
Date Mon, 28 Dec 2009 13:50:19 GMT
I sent the reply offlist. Here is it.

2009/12/28 Stefano Bagnara <apache@bago.org>:
> 2009/12/28 Florent Georges <lists@fgeorges.org>:
>> Stefano Bagnara wrote:
>>  Hi,
>>> AFAIK the header value is anything after the ":".  The space is
>>> inserted by most mime writing code around, but it is not a
>>> required separator in the mime specification.  In fact if there
>>> is a space, it is already part of the body value.
>>  So if I am right, getBody() does return the raw value of the
>> field, without for instance any unfolding of neither white spaces
>> nor comments, right?
> Currently it shows a mixed behaviour and we are trying to fix it.
> getBody should always (but it seems it doesn't in the 0.6, should do
> this in 0.7) return the unfolded value.
>>  Is there any parser in mime4j to help parsing such field values?
> It is a bit chaotic, and we're trying to decide how to expose header
> parsing. ATM you can access some parsing via Fields object and some
> other parsing via AbstractField.parse method (or, as we are going to
> remove this, I suggest you to instantiate a DefaultFieldParser class).
> Stefano

View raw message