http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html
3.6.1
All HTTP/1.1 applications MUST be able to receive and decode the
"chunked" transfer-coding, and MUST ignore chunk-extension extensions
they do not understand.
So you have to jump through big hoops to not use chunked encoding
[IIRC - This thread had to do with a CDN not caching due to chunked
encoding. A "good" CDN should be able to cache content if you pass the
appropriate cache friendly headers. (Like Etag, expires, etc) And handle
the chunked encoding for you.]
-Tim
Anthony J. Biacco wrote:
No dice. I tried a bufferSize of 16384 and an 11K response still got chunked.
Even tried using packetSize and max_packet_size (mod_jk).
-Tony
---------------------------
Manager, IT Operations
Format Dynamics, Inc.
303-573-1800x27
abia...@formatdynamics.com
http://www.formatdynamics.com
-----Original Message-----
From: Anthony J. Biacco
Sent: Thursday, June 11, 2009 2:31 PM
To: 'Tomcat Users List'
Subject: RE: chunked encoding
I tested with a >8K jsp and did get it chunked.
Do you happen to know the parameter for changing the buffer size?
Perhaps I can increase it to a number representing the largest length
of my servlet content. Which isn't too big, maybe 20K.
NM on this, I found bufferSize for the AJP connector. I'll test it out.
-Tony
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
