it seems to be the zip.dll in Java causing the
problem (check the log below), so I now turned of HTTP compression in
Tomcat.
These are the parameters we used for compression for the Connector (it's
running under port 443 on SSL).
compression=2048
noCompressionUserAgents=gozilla, traviata
because the benchmark used a Gbit
network
Thanks
Johan
ws_dev wrote:
hello,
Does Tomcat support HTTP compression.
If yes, is there a way to enable/disable this feature
Rajiv
-
To start a new topic, e-mail: users
:
hello,
Does Tomcat support HTTP compression.
If yes, is there a way to enable/disable this feature
Rajiv
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
From: Pid [mailto:p...@pidster.com]
Subject: Re: HTTP compression
?xml version=1.0 encoding=utf-8?soap:Envelope
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;soap:Body
hello,
Does Tomcat support HTTP compression.
If yes, is there a way to enable/disable this feature
Rajiv
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
See if the compression property is what you need:
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html
-Original Message-
From: Rajiv M [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 5:10 PM
To: Tomcat Users List
Subject: HTTP compression
hello,
Does Tomcat support HTTP
Thank you!
Is there a testcase/sample app where I can see the difference of
enabling/disabling HTTP compression.
On 4/27/07, Praveen Balaji [EMAIL PROTECTED] wrote:
See if the compression property is what you need:
http://tomcat.apache.org/tomcat-5.5-doc/config/http.html
-Original
On 4/27/07, Rajiv M [EMAIL PROTECTED] wrote:
Is there a testcase/sample app where I can see the difference of
enabling/disabling HTTP compression.
DIY :-)
-Rashmi
-
To start a new topic, e-mail: users@tomcat.apache.org
by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Rashmi Rubdi [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, April 27, 2007 10:36 AM
Subject: Re: HTTP compression
On 4/27/07, Rajiv M [EMAIL
you won't be able to disable the chunked encoding.
But you can disable the compression by ensure the client does NOT send a
accept-encoding header with the a value containing gzip or by using
the noCompressionUserAgents, compressableMimeType attributes on the
connector.
-Tim
wakeup wrote:
-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/AXIS%3A-tomcat-always-do-http-compression-without-watch-min-size-tf2386947.html#a6677693
Sent from the Tomcat - User mailing list archive at Nabble.com
respect compressionMinSize parameter?
Thanks
--
View this message in context:
http://www.nabble.com/AXIS%3A-tomcat-always-do-http-compression-without-watch-min-size-tf2386947.html#a6654078
Sent from the Tomcat - User mailing list archive at Nabble.com
webservices it always compress the response althought it be less
than 1kb.
Why axis don't respect compressionMinSize parameter?
Thanks
--
View this message in context: http://www.nabble.com/AXIS%3A-tomcat-
always-do-http-compression-without-watch-min-size-
tf2386947.html#a6654078
Sent from
compressionMinSize only works with fixed file sizes. If axis is NOT
setting the ContentLength before serving back results - then
compressionMinSize can't be checked to see if compression can be done.
And then compression will be done based on the client input headers.
-Tim
wakeup wrote:
Hi,
14 matches
Mail list logo
