Return-Path: 
 <dev-return-31054-apmail-hc-dev-archive=hc.apache.org@hc.apache.org>
X-Original-To: apmail-hc-dev-archive@www.apache.org
Delivered-To: apmail-hc-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C6C5D1186C
	for <apmail-hc-dev-archive@www.apache.org>;
 Wed, 17 Sep 2014 10:12:34 +0000 (UTC)
Received: (qmail 12661 invoked by uid 500); 17 Sep 2014 10:12:34 -0000
Delivered-To: apmail-hc-dev-archive@hc.apache.org
Received: (qmail 12565 invoked by uid 500); 17 Sep 2014 10:12:34 -0000
Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@hc.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@hc.apache.org>
List-Post: <mailto:dev@hc.apache.org>
List-Id: <dev.hc.apache.org>
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Delivered-To: mailing list dev@hc.apache.org
Received: (qmail 12265 invoked by uid 99); 17 Sep 2014 10:12:34 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Sep 2014 10:12:34 +0000
Date: Wed, 17 Sep 2014 10:12:34 +0000 (UTC)
From: "Oleg Kalnichevski (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.12742089.1410946363000.54003.1410948754223@Atlassian.JIRA>
In-Reply-To: <JIRA.12742089.1410946363000@Atlassian.JIRA>
References: <JIRA.12742089.1410946363000@Atlassian.JIRA>
 <JIRA.12742089.1410946363432@arcas>
Subject: [jira] [Commented] (HTTPCLIENT-1554) defaultRequestConfig never
 used in InternalHttpClient
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137023#comment-14137023 ] 

Oleg Kalnichevski commented on HTTPCLIENT-1554:
-----------------------------------------------

And what is it exactly that makes you think so?

Oleg

> defaultRequestConfig never used in InternalHttpClient
> -----------------------------------------------------
>
>                 Key: HTTPCLIENT-1554
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1554
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: 4.3.5
>         Environment: android
>            Reporter: Rob Smit
>              Labels: HttpClient
>
> after initializing builder en building client, the timeout settings are not used for the request execution. In ClosableHttpClient.doExecute(), an on the fly request config is used.
> my code:
>         builder = HttpClientBuilder.create();
>         int timeout = 30000;
>         defaultRequestConfig = RequestConfig.custom()
>                 .setSocketTimeout(timeout)
>                 .setConnectTimeout(timeout)
>                 .build();
>         builder.setDefaultRequestConfig(defaultRequestConfig);
>         List<Header> headers = new ArrayList<Header>();
>         headers.add(new BasicHeader("Accept", "application/json"));
>         builder.setDefaultHeaders(headers);
>         builder.useSystemProperties();
>         client = builder.build();
>         client.execute(request)
> timeout settings are never used!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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