Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of jslive@gmail.com designates
 209.85.142.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=xE8R7vMjpso08LPLkGdAL9DbI4O8VwU625+PX4Tl2Z3cqQzAGNMEZhSka/8F+AHAq7gxcsEGIzSWvkj83N7CXX25kl5p3vm59bcIULMKcodckK2WP3JY2t1WWZ4sExxdrzAu2AY7SbO01cC4tDKOIdQ5jA0CC4n+VW2PjnT7F+k=
Message-ID: <e498c1660804221150q4981dd73ma1f57311959dad61@mail.gmail.com>
Date: Tue, 22 Apr 2008 14:50:44 -0400
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org
In-Reply-To: <1fd4cf1b0804221143n5477aa36p8a933808f488118b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1fd4cf1b0804221143n5477aa36p8a933808f488118b@mail.gmail.com>
Subject: Re: [users@httpd] header unset content-encoding

On Tue, Apr 22, 2008 at 2:43 PM, michel platini <azalis73@gmail.com> wrote:

> the problem is that apache set the header content-encoding to be chunked
> before send the response.
> this is a problem because the client is not http\1.1 compliant and doesn't
> work if there are no content-length header.
>
> infact using browser all works fine even though in the download window there
> are no information about content length.
>
> So I ask you if you know some workaround to unable the header
> content-encoding so the client can see content-length.

It's not the header itself that is the problem, it is the chunked encoding.

The first question I'd ask is why the chunked encoding is getting sent
in the first place. Apache should only send chunked if the client
states in the request-line that it is HTTP/1.1. Is the client lying
about what it supports?

Under the assumption that you have a broken client, you can use
BrowserMatch ClientUA downgrade-1.0
See:
http://httpd.apache.org/docs/2.2/env.html#special
You may also need nokeepalive, depending on the nature of the clients problems.

None of this will actually get you a Content-Length header. Apache
can't generate that in any reasonable way, because it doesn't know the
content-length before sending the response. If you want a
Content-Length, you'll need to get resin to calculate it and send it
out.

But even an HTTP/1.0 client should be able handle a non-chunked
response without content length. The server simply closes the
connection to indicate that all the content has been sent.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org