In fact, it was a gzip compression not on Tomcat side, but in the webapp
itself (using servlet filter). I do not know whether it's better or not,
but it's how it was done.
Caldarale, Charles R wrote:
From: Baldurien [mailto:[EMAIL PROTECTED]
Subject: Re: Download problem with IE6, IIS 6.0, SSL, Tomcat
6.0.13 and connector1.2.25 (last in date) on Windows Server 2k3
I've found a reason to my problem : I was sending a Content-Length
header, albeit I was using GZIP Compression.
What I do not understand, is why the browser could get the content on
tomcat despise that header, and why the connector could not?
What is the value of the compression attribute for the HTTP <Connector>
in your Tomcat configuration? The default value is "off", which (I'm
guessing) would inhibit compression despite other settings. I don't see
a corresponding attribute for the AJP connector, so that might be a
factor in the observed behavior.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Baldurien La Bibliothèque de Neverwinter Nights
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
