[
https://issues.apache.org/jira/browse/STORM-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505583#comment-14505583
]
Derek Dagit commented on STORM-793:
-----------------------------------
Ideally we want to respond with a 404, since the log is not yet available. If
we were to do a simple null check at the linked code above, we would be
responding with an inaccurate authorization-denial message.
> Logviewer 500 response when metadata has not yet been written (with auth
> enabled)
> ---------------------------------------------------------------------------------
>
> Key: STORM-793
> URL: https://issues.apache.org/jira/browse/STORM-793
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Derek Dagit
> Priority: Minor
> Labels: Newbie
>
> When ui.filter is defined and used, and a user navigates to a logviewer link
> for which the logging metadata has not yet been initialized, we [throw an
> NPE|https://github.com/apache/storm/blob/84e8bc6d28b54056dd75375be7d316ab03125fb6/storm-core/src/clj/backtype/storm/daemon/logviewer.clj#L184]
> that results in a 500 response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
