Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Subject: Re: mod_deflate ignores Content-Encoding header
From: Nick Kew <nick@webthing.com>
To: dev@httpd.apache.org
In-Reply-To: <ehqkp5$d2o$1@sea.gmane.org>
References: <ehqkp5$d2o$1@sea.gmane.org>
Content-Type: text/plain; charset=utf-8
Date: Sat, 28 Oct 2006 16:35:26 +0100
Message-Id: <1162049726.11522.16.camel@grimnir>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

On Thu, 2006-10-26 at 17:38 +0200, Sven Köhler wrote:
> Hi,
> 
> imagine a simple CGI-script:
> 
> 
> #!/usr/bin/perl
> print "Content-Encoding: identity\n";
> print "Content-Type: text/plain\n";
> print "\n";
> print "test";
> 
> 
> AFAIK, "identity" indicates, that no transformation is being done on the
> content.
> 
> IMHO, mod_deflate should implement the following logic:
> 
> Content-Encoding-header already present?
>   yes: do nothing, just forward content
>   no: add Content-Encoding header and do compression

It's a valid behaviour.  So's the current one.

Putting it under the control of the admin is a reasonable
proposition.  mod_filter does that: you can conditionally
insert mod_deflate.

-- 
Nick Kew