On Wed, Jul 8, 2015 at 12:52 PM, Sean Dawson <seandawson2...@gmail.com> wrote:
> > Hello, we have a GWT 2.7 application that's deployed on tomcat7 (r57-63) > that uses RestyGwt to make REST calls to another server (which uses > RestEasy 3.11). > > We're seeing several issues that seem to be clustered into two categories > (transferring binary data, exceptions with xml data) - with one overriding > theme (content length isn't correct - this is the application server > exception we see, and fiddler shows the same thing). > Here's what I found out... - RestEasy sets the Content-Length to the exception length when it gets thrown - If the proxy sends back less info (without changing CL), tomcat/the-browser waits for a certain period and then times out / fails; and fiddler complains about a mismatch CL - if the proxy sends back MORE info (without changing CL), tomcat/the-browser gets back the data sent *up to the limit of CL*; no one complains - if the proxy properly adjusts the CL, everything is fine Does tomcat perform any semantic checks on the contents of outgoing HTTP messages, e.g. (in our case) raising some kind of error/event if there is a content-length mismatch?
