[
https://issues.apache.org/jira/browse/KNOX-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Minder resolved KNOX-502.
-------------------------------
Resolution: Fixed
Confirmed that the audit log now contains entries for 404s. See below for an
example.
{code}
5/12/23 10:54:27
||5a8b3cc7-e70d-4598-b7cd-4381013f6217|audit|||||access|uri|/gateway/sandbox/gateway/wrong|unavailable|Request
method: GET
15/12/23 10:54:27
||5a8b3cc7-e70d-4598-b7cd-4381013f6217|audit|||||access|uri|/gateway/sandbox/gateway/wrong|success|Response
status: 404
15/12/23 10:55:13
||2f45d4da-79bb-4ed8-a15d-3eb2c33a7768|audit|||||access|uri|/gateway/sandbox/wrong|unavailable|Request
method: GET
15/12/23 10:55:13
||2f45d4da-79bb-4ed8-a15d-3eb2c33a7768|audit|||||access|uri|/gateway/sandbox/wrong|success|Response
status: 404
{code}
> Invalid requests (404s) should be logged and audited
> ----------------------------------------------------
>
> Key: KNOX-502
> URL: https://issues.apache.org/jira/browse/KNOX-502
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.5.0
> Reporter: Kevin Minder
> Fix For: 0.7.0
>
>
> Currently there is no Knox level diagnostic or audit information produced for
> 404s. This has been making it difficult for users to self diagnose
> mismatches between their perception of a cluster name and a topology name.
> We should provide better diagnostics here to help the users figure out what
> the problem is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
