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
>
>
-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 sur
:
maxKeepAliveRequests="1" in server.xml
> Date: Thu, 6 Jan 2011 16:08:36 -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: S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ilya,
On 1/6/2011 12:27 PM, ilya goberman wrote:
> I think what was suggested before is to control this behavior by
> setting "keepAlive" setting. I would not think this is the right
> way.
Er, what's the difference between using "keepAlive setting"
nse and
chunked encoding is not necessary in this case.
> Date: Thu, 6 Jan 2011 12:12:37 -0500
> From: ch...@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProtocol
> connector.
>
> -BEGIN PGP SIG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 1/5/2011 5:13 PM, André Warnier wrote:
> 4.3 Message Body
> ...
> Transfer-Encoding is a property of the message, not of the
> entity, and thus MAY be added or removed by any application along the
> request/response chain.
Maybe the OP shou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ilya,
On 1/5/2011 4:29 PM, ilya goberman wrote:
> I was thinking more about it. What if Tomcat disables chunked
> encoding if response contains "Connection: close" header.
I think that's what Mark has suggested several times, now:
On 1/5/2011 12:54
nd work
around some bugs, I would take it.
Thanks
> Date: Wed, 5 Jan 2011 23:13:07 +0100
> From: a...@ice-sa.com
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProtocol
> connector.
>
> Correct me if I am wrong, but it seems to
Correct me if I am wrong, but it seems to me that both in the case of this post, and
another simultaneous one entitled "Tomcat and HTTP chunk extensions", the OP's are trying
to use HTTP in a way that is not really part of the protocol design.
The transfer-encoding is not supposed to be something
ilya goberman wrote:
I was thinking more about it. What if Tomcat disables chunked encoding if response
contains "Connection: close" header.
So in order to disable the encoding the Tomcat application will have to set
just one response header.
I think it is a reasonable enhancement to do. If "C
tion: close" is not
set, keep alive functionality is preserved.
Any objections?
> Date: Wed, 5 Jan 2011 17:54:53 +
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProtocol
> connector.
>
>
OK, it is fair, thanks.
> Date: Wed, 5 Jan 2011 17:54:53 +
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProtocol
> connector.
>
> On 05/01/2011 17:43, ilya goberman wrote:
> >
> > M
nd is
not intended for more general discussion.
Mark
> Thanks
>
>> Date: Wed, 5 Jan 2011 16:38:20 +
>> From: ma...@apache.org
>> To: users@tomcat.apache.org
>> Subject: Re: How to disable chunked encoding for the Http11NioProtocol
>> connector.
>&g
2011 16:38:20 +
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProtocol
> connector.
>
> On 05/01/2011 15:29, ilya goberman wrote:
> >
> > Mark, overhead of chunked encoding can be significant
cement to optionally restore the
non-chunked approach when keep-alive is disabled. I'm not sure how much
interest there will be in implementing it though.
Mark
> Thanks
>
>> Date: Wed, 5 Jan 2011 06:14:18 +0000
>> From: ma...@apache.org
>> To: users@tomcat.apache.org
iated with chunked
encoding, so disabling it is the only way for these to work properly.
> Date: Wed, 5 Jan 2011 17:01:57 +0100
> From: ronald-mailingl...@base.nl
> To: users@tomcat.apache.org
> Subject: RE: How to disable chunked encoding for the Http11NioProtocol
> connector.
>
omcat issue, it will score some points for
Tomcat if this is addressed by adding a configuration option.
Thanks
> Date: Wed, 5 Jan 2011 06:14:18 +
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProtocol
con
s not a Tomcat issue, it will score some points for
Tomcat if this is addressed by adding a configuration option.
Thanks
> Date: Wed, 5 Jan 2011 06:14:18 +
> From: ma...@apache.org
> To: users@tomcat.apache.org
> Subject: Re: How to disable chunked encoding for the Http11NioProt
On 05/01/2011 05:04, ilya goberman wrote:
>
> Hi,
> I use NIO HTTP Tomcat connector org.apache.coyote.Http11NioProtocol to
> implement Comet streaming to browsers and mobile devices.
>
> I would like to disable HTTP response chunked encoding to reduce bandwidth.
How significant is the overhead
Hi,
I use NIO HTTP Tomcat connector org.apache.coyote.Http11NioProtocol to
implement Comet streaming to browsers and mobile devices.
I would like to disable HTTP response chunked encoding to reduce bandwidth.
The response will have header "Connection: close" with "Content-Length" header
omitted
20 matches
Mail list logo
