Return-Path: X-Original-To: apmail-hc-httpclient-users-archive@www.apache.org Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD81211AC0 for ; Thu, 25 Sep 2014 06:36:45 +0000 (UTC) Received: (qmail 34854 invoked by uid 500); 25 Sep 2014 06:36:45 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 34810 invoked by uid 500); 25 Sep 2014 06:36:45 -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 34793 invoked by uid 99); 25 Sep 2014 06:36:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Sep 2014 06:36:44 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of solomax666@gmail.com designates 209.85.192.172 as permitted sender) Received: from [209.85.192.172] (HELO mail-pd0-f172.google.com) (209.85.192.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Sep 2014 06:36:40 +0000 Received: by mail-pd0-f172.google.com with SMTP id fp1so490584pdb.3 for ; Wed, 24 Sep 2014 23:36:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=tFKekBgC998a83jCMLB0xjKvE+BdWYbvbQkdTsYPyq8=; b=0/uiBan6xKqRaC1RgMu4zYLXabUHpDGnbXN8sWSEz0lXDroG8LyAvbxQtnOzj5ZAUb XFO93QzEMvGw2IypRHRj0DMRJUjjz/27hyt5ayMiv8eKvuSvY5XF2U/p3NbR4HlXBSfk wiiyEOUmbwyXxGabeA69IuZTZ5FdHoYQI5JaWKhJI3DHbI0fHIgO5Kop3+UeMyYhY4M/ B8ENrxahgw/d8T1wVv2P9K1RKR5lZyw839xvI5DDc9r2q5skgbVhCZTEmYJRDA1F/xjl ewpJnYBZjXr9UdrPd/3jHnp4vNpj8aE2X9LiyxSJaMAlkEYLn9lD/fwwi9ypDuv1vlAA VR6Q== MIME-Version: 1.0 X-Received: by 10.68.249.101 with SMTP id yt5mr15536253pbc.156.1411626980009; Wed, 24 Sep 2014 23:36:20 -0700 (PDT) Received: by 10.67.1.4 with HTTP; Wed, 24 Sep 2014 23:36:19 -0700 (PDT) Date: Thu, 25 Sep 2014 13:36:19 +0700 Message-ID: Subject: Http_1_1 and strict-transfer-encoding using client 4.3 From: Maxim Solodovnik To: httpclient-users@hc.apache.org Content-Type: multipart/alternative; boundary=047d7b671d76b2ee320503de04d5 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b671d76b2ee320503de04d5 Content-Type: text/plain; charset=UTF-8 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) 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 Thanks in advance [1] http://httpcomponents.10934.n7.nabble.com/how-to-change-content-length-strategy-td19040.html -- WBR Maxim aka solomax --047d7b671d76b2ee320503de04d5--