On Thu, 2014-09-25 at 17:20 +0700, Maxim Solodovnik wrote: > Thanks for the answers, > > 1) the code you have provided is for setting protocolVersion for request > not client, the question was is it possible to set protocolVersion to the > client? >
HttpClient protocol version is always HTTP/1.1. Protocol version settable at the client level was a mistake. Oleg > 2) Is there any example? I found [1], but it is not compilable. > Additionally it seems like currently I need to write lot more code like > before :( > > > [1] > http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/201301.mbox/%3C1359388867.10617.16.camel@ubuntu%3E > > On 25 September 2014 16:21, Oleg Kalnichevski <[email protected]> wrote: > > > On Thu, 2014-09-25 at 13:36 +0700, Maxim Solodovnik wrote: > > > Hello All, > > > > > > I have couple of questions according migration to client 4.3 > > > 1) Is it possible to created client operating Http_1_1? It is possible to > > > set protocol version for each request, but I would like to tell client to > > > work over protocol version 1.1. (was previously possible) > > > > --- > > HttpGet httpGet = new HttpGet("https://host/stuff";); > > httpGet.setProtocolVersion(HttpVersion.HTTP_1_0); > > --- > > > > > 2) Is there any example of setting "strict-transfer-encoding"? The one I > > > found here [1] seems to be outdated and requires too much code comparing > > to > > > previous version > > > > > > > A lot of marginally useful parameters got deprecated including the so > > called "strict-transfer-encoding" parameter. Custom content length > > strategy is the way to go. > > > > Oleg > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
