This is almost certainly the same as the known bug in GWT hosted mode with no-entity responses. If the order of writing this header fixes the problem transparently, it would be awesome to do it!
On Mon, Jan 5, 2009 at 5:45 PM, Eirik Bjørsnøs <eir...@gmail.com> wrote: > Setting the Content-Length to 0 on Tomcat 5.0.x effectively prevents > any other headers or status coded being set because the response is > considered to be committed according to the servlet spec.
