Also, if HTTP 1.1 weren't enabled for some reason, wouldn't the default simply be to serve the entire content, rather than the first 16384 bytes?
On Tue, Dec 3, 2013 at 4:44 PM, C. Benson Manica <cbman...@gmail.com> wrote: > <Connector port="8080" protocol="HTTP/1.1" > connectionTimeout="20000" > redirectPort="8443" /> > > sure looks like 1.1 to me. > > > On Tue, Dec 3, 2013 at 4:38 PM, Martin Gainty <mgai...@hotmail.com> wrote: > >> chunked only works on HTTP 1.1 connections >> display $CATALINA_HOME/conf/server.xml >> >> Martin-- >> >> >> >> >> >> > Date: Tue, 3 Dec 2013 15:55:22 -0800 >> > Subject: Transfer-Encoding: chunked not working >> > From: cbman...@gmail.com >> > To: users@tomcat.apache.org >> > >> > Tomcat 7.0.47, OSX 10.8. Fresh install via homebrew. I'm running a web >> app >> > with Tomcat that is returning the header "Transfer-Encoding: chunked" >> and >> > seemingly exactly one 16384-byte chunk of content that is longer than >> that. >> > Consequently the page that should be transferred is not rendered by the >> > user agent (Chrome in this case). AFAICT it's Tomcat that isn't sending >> all >> > the chunks properly. Why might it not be doing that? What else might be >> the >> > problem? >> > >> > -- >> > C. Benson Manica >> > cbman...@gmail.com >> >> > > > > -- > C. Benson Manica > cbman...@gmail.com > -- C. Benson Manica cbman...@gmail.com
