hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HTTPCLIENT-1470) CachingExec(ClientExecChain backend, HttpCache cache, CacheConfig config, AsynchronousValidator asynchRevalidator) NPE if config is null
Date Sun, 23 Feb 2014 03:08:20 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb updated HTTPCLIENT-1470:
-----------------------------

    Fix Version/s: 4.4 Alpha1

> 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.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


Mime
View raw message