Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <002301c4c289$045fc5b0$ceeb10ac@sappling>
From: "Steve Appling" <sajakarta@mindspring.com>
To: <tomcat-dev@jakarta.apache.org>
Subject: Coyote Connector - Disabling compression for a specific servlet
Date: Thu, 4 Nov 2004 11:11:58 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I have an application where I would like to disable gzip compression for a few specific pages /
servlets.  I originally planned to use a servlet filter to remove gzip from the accept-encoding
header on the request, but this won't work.  The container code that needs to check this
(isCompressable method on Http11Processor) doesn't see the filtered request headers, but does see
the response headers (this makes sense in retrospect).

What does everyone think about supporting a special response header that could be used to disable
compression on a particular request (something like X-NoCompress)?  I'm not sure if there is a
header used for something like this in other applications.  I know there are stand-alone hardware
boxes sold to handle HTTP compression outside of the web server.  Do any of them support a similar
mechanism to disable compression on a per request basis?


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org