I've used tomcat since 2001 with our database sync product, use sysdeo in eclipse, etc. and tomcat 4.1.3 has been working fine.
We have a new feature to do content-encoding: gzip and I tried tomcat 5.5 and tomcat 5.0 which have the following in server.xml: compression="on" compressionMinSize="2048" noCompressionUserAgents="gozilla, traviata" compressableMimeType="text/html,text/xml" So without turning it on in 5.5 or 5.0 I tried our product which does POSTs to our servlet. There are 4 msgs that return no data that work fine, then the request which should return data always returns 0 bytes, content-length=0, din.available() = 0. I've run it through an http sniffer and the response from the server ends with: 0210: 6F 76 67 71 45 46 42 65 46 62 66 48 44 0D 0A 43 ovgqEFBeFbfHD..C 0220: 6F 6E 74 65 6E 74 2D 4C 65 6E 67 74 68 3A 20 30 ontent-Length: 0 0230: 0D 0A 44 61 74 65 3A 20 54 68 75 2C 20 31 34 20 ..Date: Thu, 14 0240: 4F 63 74 20 32 30 30 34 20 32 31 3A 31 31 3A 34 Oct 2004 21:11:4 0250: 32 20 47 4D 54 0D 0A 53 65 72 76 65 72 3A 20 41 2 GMT..Server: A 0260: 70 61 63 68 65 2D 43 6F 79 6F 74 65 2F 31 2E 31 pache-Coyote/1.1 0270: 0D 0A 0D 0A .... Is there anything new to v5 which anyone can think of which might cause my data to not be returned? Its still HTTP 1.1 and our server runs on many different web servers without a problem. At first I thought i was getting chunked data, but there is no length in the CRLF's its a typical java client using java.net classes. thanks very much for your time and thoughts ... Dave Been
