[
https://issues.apache.org/jira/browse/KNOX-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916065#comment-16916065
]
ASF subversion and git services commented on KNOX-1995:
-------------------------------------------------------
Commit 32c3f2d4b727697c26c6022dd6051b0a28d6f4df in knox's branch
refs/heads/master from Kevin Risden
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=32c3f2d ]
KNOX-1995 - If a rule doesn't match, shouldn't error. Need to handle null case
Closes #135
Signed-off-by: Kevin Risden <[email protected]>
> If a rule doesn't match, shouldn't error. Need to handle null case
> ------------------------------------------------------------------
>
> Key: KNOX-1995
> URL: https://issues.apache.org/jira/browse/KNOX-1995
> Project: Apache Knox
> Issue Type: Bug
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently when an explicit rule doesn't match, we are throwing an ERROR and
> returning null. This causes NPEs later in the flow and instead should match
> the behavior of a non explicit rule. If the rule doesn't match, log only at
> DEBUG and return the original input.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
