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 >
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 versions. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
