Uploaded image for project: 'HttpComponents HttpClient'
  1. HttpComponents HttpClient
  2. HTTPCLIENT-1470

CachingExec(ClientExecChain backend, HttpCache cache, CacheConfig config, AsynchronousValidator asynchRevalidator) NPE if config is null

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.3.2, 4.4 Alpha1
    • Fix Version/s: 4.3.4, 4.4 Alpha1
    • Component/s: HttpCache
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sebb Sebb
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: