hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: Making CharsetEncoder/CharsetDecoder CodingErrorAction to be configurable
Date Sat, 24 Sep 2011 11:20:26 GMT
On Sat, 2011-09-24 at 11:52 +0530, Rajika Kumarasiri wrote:
> Hello,
> Due to various character encoding complexities such as the system is
> configured to receive UTF-16 and but receives UTF-8 streams etc.. following
> exception throws by the httpcore library[0].
> At this point the connection will be dropped. But upon receiving this kind
> of errors we can recover if we configure  CharsetEncoder/CharsetDecoder with
> a CodingErrorAction [1] where the action can be report (default), ignore and
> resume or replace and resume the coding logic. I think this choice should be
> a configuration option in  SessionInputBufferImpl/SessionOutputBufferImpl
> constructors.
> I was hoping we can fix this by adding two string constant
> 'http.malformed.input.action' and 'http.unmappble.input.action'
> into CoreProtocolPNames interface so that we can query using
> BasicHttpParams. But it seems CoreProtoclPNames is a core interface which we
> can't change directly.
> Do let me know your comments. Thanks.
> Rajika


I see no reason why CoreProtocolPNames cannot be extended with
additional parameters, which are basically static variables, and
therefore should have no impact on binary compatibility with previous


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

View raw message