On 6/25/12 9:19 AM, Au, Leon leo...@amazon.com wrote:
Hi,
There was a recent change to how Tomcat handles the Content-Type response
header in order to address Bug #52811
(https://issues.apache.org/bugzilla/show_bug.cgi?id=52811)
We've noticed that this can cause issues with client code when
On 26/06/2012 23:26, Au, Leon wrote:
On 6/25/12 9:19 AM, Au, Leon leo...@amazon.com wrote:
Hi,
There was a recent change to how Tomcat handles the Content-Type response
header in order to address Bug #52811
(https://issues.apache.org/bugzilla/show_bug.cgi?id=52811)
We've noticed that
Hi,
There was a recent change to how Tomcat handles the Content-Type response
header in order to address Bug #52811
(https://issues.apache.org/bugzilla/show_bug.cgi?id=52811)
We've noticed that this can cause issues with client code when parsing the
response. We traced the issue to that fact