hc-httpclient-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Panchenko <alex.panche...@gmail.com>
Subject Re: 400 bad request POSTing to Tomcat 7.0.42
Date Tue, 03 Mar 2015 08:47:46 GMT
I am curious about how the client code looks now, before we continue
complaining on the other end.
Just trying to be fair.

On Tue, Mar 3, 2015 at 2:36 PM, Brett Ryan <brett.ryan@gmail.com> wrote:

> > What confused me, is that I thought that tomcat should honor the
> encoding set inside xml, while it just use content-type encoding or its
> default one instead.
> Thats the correct behaviour. Your servlet container may choose to inspect
> the POST data but there is no requirement for it to, thats up to you to
> implement a filter as mentioned earlier. What if your XML was malformed,
> what do you think it should do? The content could be anything for all it
> cares. What would your processor do if the header of the XML said the
> encoding was 8859-1, but the actual encoding was UCS-2? You wouldn't even
> be able to read the header reliably, you would have to perform a series of
> rereads to get the right encoding.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> For additional commands, e-mail: httpclient-users-help@hc.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message