Return-Path: 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 54A30CE5B for ; Wed, 30 May 2012 18:10:24 +0000 (UTC) Received: (qmail 74130 invoked by uid 500); 30 May 2012 18:10:24 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 73820 invoked by uid 500); 30 May 2012 18:10:24 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 73786 invoked by uid 99); 30 May 2012 18:10:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2012 18:10:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id AAE2B140C2C for ; Wed, 30 May 2012 18:10:23 +0000 (UTC) Date: Wed, 30 May 2012 18:10:23 +0000 (UTC) From: "Jon Moore (JIRA)" To: dev@hc.apache.org Message-ID: <927782393.17309.1338401423701.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1985112493.16758.1338393623834.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (HTTPCLIENT-1198) HttpHost is not set in HttpContext in CachingHttpClient 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-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1198: ---------------------------------- Component/s: Cache Affects Version/s: 4.1.3 Fix Version/s: 4.2.1 Right, the CachingHttpClient relies on the "backend" client to fill these parts of the HttpContext out. When the CachingHttpClient serves a response out of cache, they don't get set, however. It should be possible to set some (but not all) of the usual HttpContext variables. For example, we can't set HTTP_CONNECTION or HTTP_PROXY_HOST on a cache hit. > HttpHost is not set in HttpContext in CachingHttpClient > ------------------------------------------------------- > > Key: HTTPCLIENT-1198 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1198 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: Cache, HttpClient > Affects Versions: 4.1.3, 4.2 Final > Reporter: Ilirjan Papa > Priority: Critical > Fix For: 4.2.1 > > > The HttpHost cames back as null, causing a NullPointerException when using CachingHttpClient. > HttpHost actualHost = (HttpHost)requestContext.getAttribute(ExecutionContext.HTTP_TARGET_HOST); > The host should be set in the HttpContext. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org