Got it, thanks

> Date: Thu, 6 Jan 2011 16:34:40 -0500
> From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProtocol 
> connector.
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ilya,
> 
> On 1/6/2011 4:17 PM, ilya goberman wrote:
> > OK. All I wanted to say is that disabling keepAlive across the board
> > is not necessary.
> 
> Nobody is suggesting that.
> 
> > If keepAlive can be applies to a single response
> > (and to be honest I am not sure it is possible), it is fine.
> 
> Of course it can: headers can be set on a per-response basis. Otherwise,
> stuff like Content-Type and Content-Length would never work.
> 
> > I was under impressing that the only way to disable keep alive is
> > globally via: maxKeepAliveRequests="1" in server.xml
> 
> That's obviously the wrong approach.
> 
> File another enhancement request to allow configuration to let client
> and/or server use of "Connection:close" to disable chunked response
> encoding and I'm sure Mark won't mark it as INVALID or WONTFIX.
> 
> It's possible nobody will actually submit a patch for it any time soon,
> but you are free to do so. Enhancement requests with accompanying
> patches are much more likely to be fixed. ;)
> 
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAk0mNXAACgkQ9CaO5/Lv0PCsPACfQpD5JEO8QEDyoaQQFg2TqN7f
> 3+MAn3N/RJa+j63Wp67tJL5Tw3J6twrY
> =u9Rn
> -----END PGP SIGNATURE-----
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
                                          

Reply via email to