You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (Jira)" <ji...@apache.org> on 2019/08/26 17:13:00 UTC
[jira] [Updated] (KNOX-1995) If a rule doesn't match, shouldn't
ERROR and return null
[ https://issues.apache.org/jira/browse/KNOX-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Risden updated KNOX-1995:
-------------------------------
Status: Patch Available (was: In Progress)
> If a rule doesn't match, shouldn't ERROR and return null
> --------------------------------------------------------
>
> 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: 10m
> 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)