A while back, I was working with a
soap client that couldn't handle chunked responses. I was able to get Tomcat to send unchunked data by changing the HTTP version in the request to HTTP/1.0 (HTTP/1.1 is the default for most browsers these days).
This was done from the client itself, not from within Tomcat.
From:
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html
HTTP/1.1 and HTTP/1.0 Support
This Connector supports all of the required features of the HTTP/1.1 protocol, as described in RFC 2616, including persistent connections, pipelining, expectations and chunked encoding. If the client (typically a browser) supports only HTTP/1.0, the Connector will gracefully fall back to supporting this protocol as well. No special configuration is required to enable this support. The Connector also supports HTTP/1.0 keep-alive.
RFC 2616 requires that HTTP servers always begin their responses with the highest HTTP version that they claim to support. Therefore, this Connector will always return HTTP/1.1 at the beginning of its responses.
[ October 17, 2006: Message edited by: Ben Souther ]