Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <1389258372.19295.9.camel@ubuntu>
Subject: Re: adding interceptors on per request basis (was Re: Unable to see
 response encoding even through "Content-Encoding" header is present)
From: Oleg Kalnichevski <olegk@apache.org>
To: HttpClient User Discussion <httpclient-users@hc.apache.org>
Date: Thu, 09 Jan 2014 10:06:12 +0100
In-Reply-To: 
 <CAFUy1TzzJ3pUt4s_CyQC3vP4o_NZFW48W+KpqJZx+4YHY-g26A@mail.gmail.com>
References: 
	<CAFUy1TzzJ3pUt4s_CyQC3vP4o_NZFW48W+KpqJZx+4YHY-g26A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2014-01-08 at 18:29 -0800, Gaurav Kumar wrote:
> Thanks! I am now able to see content-encoding. However, the example I
> followed showed how to add interceptors on global client instance level -
> is there a way I can add interceptor on per-request basis?
> 
> 

Protocol interceptors are meant for cross-cutting aspects that apply to
all messages processed by the same protocol processor. They make no
sense on per request basis. 

If you want full control over content encoding on per request basis then
you should disable automatic content decompression.

Oleg


> On Wed, Jan 8, 2014 at 8:11 AM, Oleg Kalnichevski <olegk@apache.org> wrote:
> 
> > On Wed, 2014-01-08 at 07:17 -0800, Gaurav Kumar wrote:
> > > So what is the best way to figure out what encoding is being used?
> > >
> >
> > By using a protocol interceptor.
> >
> > Oleg
> >
> > > On Jan 8, 2014 2:28 AM, "Oleg Kalnichevski" <olegk@apache.org> wrote:
> > > >
> > > > On Wed, 2014-01-08 at 00:04 -0800, Gaurav Kumar wrote:
> > > > > Using HttpClient 4.3-beta2.
> > > > >
> > > > > Have a look at this httpclient header log (headers only)
> > > > > http://pastebin.com/kWk6rbJ2
> > > > >
> > > > > As you can see, the server is responding with Content-Encoding
> > header.
> > > > >
> > > > > Now, refer to this Java code - http://pastebin.com/i7nhAksb - it
> > simple
> > > > > prints the headers and a message if content encoding cannot be found.
> > > The
> > > > > output of this code is here- http://pastebin.com/WtkuBsZb
> > > > >
> > > > >
> > > > > My question is - why HttpClient is not able to see content encoding
> > even
> > > > > though it's  header log  shows it got the header from server?
> > > > >
> > > >
> > > > Content-Length, Content-Encoding, Content-MD5 headers are removed by
> > > > ResponseContentEncoding as they no longer agree with the properties of
> > > > automatically decompressed response entity.
> > > >
> > > > Oleg
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > > > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> > > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
> > For additional commands, e-mail: httpclient-users-help@hc.apache.org
> >
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org