cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <>
Subject Re: Charset encoding other than UTF-8 (as ISO-8859-1) not working (CXF 2.7.8)
Date Wed, 02 Apr 2014 11:50:59 GMT
On 02/04/14 12:45, Jose MarĂ­a Zaragoza wrote:
> 2014-04-02 13:29 GMT+02:00 Sergey Beryozkin <>:
>> No, it is not that simple. Besides this text:
>> "The "charset" parameter is used with some media types to define the
>> character set (section 3.4) of the data. When no explicit charset parameter
>> is provided by the sender, media subtypes of the "text" type are defined to
>> have a default charset value of "ISO-8859-1" when received via HTTP"
>> seems very outdated, applies to text/* only, seems to be talking about the
>> senders only and is not available in HTTPBIS specs (I can't see it at
>> least), it does not make sense to implement it
> Yes, you're right .
> But i need to face different interpretations by my clients about this
> rule .  Damn realpolitik ... :-)
I think it is OK telling clients gently that may be their interpretation 
is not technically correct; but in the end of the day you can simply add 
a filter that will add "charset=ISO-8859-1" to Content-Type if it is 
missing a charset

Cheers, Sergey
>> Sergey
>>> Anyway, with your permission, I going to make a local fork of
>>> . Indeed, default encoding could be a good candidate
>>> to be a set property
>>> Thanks and regards

View raw message