You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2014/02/25 11:02:21 UTC
[jira] [Resolved] (HTTPCLIENT-1470) CachingExec(ClientExecChain
backend, HttpCache cache, CacheConfig config, AsynchronousValidator
asynchRevalidator) NPE if config is null
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-1470.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 4.3.4
> CachingExec(ClientExecChain backend, HttpCache cache, CacheConfig config, AsynchronousValidator asynchRevalidator) NPE if config is null
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1470
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1470
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpCache
> Affects Versions: 4.3.2, 4.4 Alpha1
> Reporter: Sebb
> Fix For: 4.3.4, 4.4 Alpha1
>
>
> The ctor CachingExec(ClientExecChain backend, HttpCache cache, CacheConfig config, AsynchronousValidator asynchRevalidator) will throw NPE if config is null.
> It allows config to be null, and defaults to CacheConfig.DEFAULT.
> However it then proceeds to re-use the config parameter rather than the instance field it has just set up.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org