Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
From: alopresto <git@git.apache.org>
To: issues@nifi.apache.org
Reply-To: issues@nifi.apache.org
References: <git-pr-999-nifi@git.apache.org>
In-Reply-To: <git-pr-999-nifi@git.apache.org>
Subject: [GitHub] nifi issue #999: NIFI-2266 Enabled TLSv1.1 and TLSv1.2 protocols for GetHTTP...
Content-Type: text/plain
Message-Id: <20160913212655.AD603E00D6@git1-us-west.apache.org>
Date: Tue, 13 Sep 2016 21:26:55 +0000 (UTC)
archived-at: Tue, 13 Sep 2016 21:26:57 -0000

Github user alopresto commented on the issue:

    https://github.com/apache/nifi/pull/999
  
    And, of course, as soon as I comment, it hits me -- `GetHTTP`, unlike `PostHTTP`, does not require a flowfile input in order to execute. So when I copied the tests I had written for `PostHTTP`, I needed to either remove the `enqueue` action of the message content prior to running, or assert that 2 flowfiles succeeded (the one manually enqueued and the result of the `GET` call). I think the current code is correct and successful, but if desired, I can push my latest changes which remove the manual enqueuing and assert explicitly 1 flowfile succeeded. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---