-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John,
On 3/31/2010 9:37 AM, John Dunne wrote: > The file is 140 kilobytes. Tomcat has no limitations on response size: it's all streaming as far as Tomcat is concerned. We routinely send large static and dynamic documents through Tomcat 5.5.25/26 without a problem. > On 31/03/2010 10:51, John Dunne wrote: >> I'm using tomcat 5.5.28 to serve an XML document (an RSS feed >> actually) via a servlet. An RSS client makes the request via a HTTP >> POST request, and I can see the servlet serves the entire XML >> document, however, the RSS client for some reason does not receive >> a complete document. I've assumed that this is to do with a >> configurable limit in the tomcat server, and after searching high >> and low on Google I've come here to see if anyone can shed some >> light on this elusive (at least for me) property. Can you confirm with a packet sniffer that the entire document is being sent across the wire? I wonder if you just need to add an out.flush() at the end of the whole thing. Another possibility is that you are sending the wrong Content-Length. Are you computing your own Content-Length and sending it? You might want to check it against the actual number of bytes you are sending to the client. Remember: Content-Length is in bytes, not characters. If you're using a character encoding that uses more than 1 byte per character, you may be sending a Content-Length that is too small to the client. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuzUwEACgkQ9CaO5/Lv0PB7OQCgvjIHkuzS4q8RN/qIQK0oXgpm 80cAnRfpA6NKN45f2CfnRTwpIcDwDOo9 =Aelz -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
