You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2016/02/11 18:45:18 UTC
[jira] [Commented] (NIFI-1504) InvokeHttp hits NPE if target system
doesn't respond with proper HTTPS Headers
[ https://issues.apache.org/jira/browse/NIFI-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143132#comment-15143132 ]
Joseph Witt commented on NIFI-1504:
-----------------------------------
recommend this not be an 0.5.0 target given its nature. good for next release.
> InvokeHttp hits NPE if target system doesn't respond with proper HTTPS Headers
> -------------------------------------------------------------------------------
>
> Key: NIFI-1504
> URL: https://issues.apache.org/jira/browse/NIFI-1504
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Joseph Percivall
> Priority: Trivial
> Labels: beginner
>
> In testing the 0.5.0 RC I found a small bug in InvokeHttp that occurs when the target System doesn't return proper headers when running HTTPS. This line[1] is where it occurs. Without doing too much digging, I believe it occurs because the target system isn't filling out a peer principal or name of the peer principal.
> Instead of NPE it should do proper checking for the values before attempting to use them.
> [1] https://github.com/apache/nifi/blob/0db2dc9fc3466051869bbf7ad8b2961405554d80/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java#L941-L941
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)