Return-Path: Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: (qmail 44433 invoked from network); 19 Oct 2008 01:09:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Oct 2008 01:09:06 -0000 Received: (qmail 25817 invoked by uid 500); 19 Oct 2008 01:09:07 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 25796 invoked by uid 500); 19 Oct 2008 01:09:07 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 25785 invoked by uid 99); 19 Oct 2008 01:09:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Oct 2008 18:09:07 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Oct 2008 01:07:57 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KrMmY-0004lM-6V for httpclient-users@hc.apache.org; Sat, 18 Oct 2008 18:08:34 -0700 Message-ID: <20052251.post@talk.nabble.com> Date: Sat, 18 Oct 2008 18:08:34 -0700 (PDT) From: cowwoc To: httpclient-users@hc.apache.org Subject: Re: HTTP compression In-Reply-To: <1224366954.6107.11.camel@ubuntu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: cowwoc@bbs.darktech.org References: <20049249.post@talk.nabble.com> <1224366954.6107.11.camel@ubuntu> X-Virus-Checked: Checked by ClamAV on apache.org I am glad to see this works, but I am surprised that server to client compression is not handled more seamlessly out-of-the-box. I was actually wondering about client to server GZip compression (that is, compressing even the request). Gili olegk wrote: > > On Sat, 2008-10-18 at 10:57 -0700, cowwoc wrote: >> Hi, >> >> I'm wondering why HTTP Client doesn't support HTTP compression >> (http://en.wikipedia.org/wiki/HTTP_compression). Will you seriously >> entertain a RFE for this feature if I file one? >> >> Thank you, >> Gili > > Gili > > If you are using HttpClient 4.0 you can easily add support for content > compression by adding a few custom protocol interceptors. > > Please refer to this example for details: > > http://svn.apache.org/repos/asf/httpcomponents/httpclient/trunk/module-client/src/examples/org/apache/http/examples/client/ClientGZipContentCompression.java > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org > For additional commands, e-mail: httpclient-users-help@hc.apache.org > > > -- View this message in context: http://www.nabble.com/HTTP-compression-tp20049249p20052251.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org