[
https://issues.apache.org/jira/browse/NIFI-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto updated NIFI-7658:
--------------------------------
Description:
Every WAR loaded by NiFi now prints two INFO logs at startup due to the default
maximum web request size being unpopulated by default. This log severity should
be lowered and the message suppressed by default as it is an expected scenario
but causes concern for many users.
{code}
2020-07-17 16:15:46,429 INFO [main] org.apache.nifi.web.server.JettyServer
Can't parse valid max content length from
2020-07-17 16:15:46,429 INFO [main] org.apache.nifi.web.server.JettyServer Not
adding content-length filter because nifi.web.max.content.size is not set in
nifi.properties
{code}
A follow-on Jira should address removing the unnecessary request entirely.
was:
All unsecured instances report an INFO log at startup and on additional
requests due to the Kerberos authentication mechanism being unavailable. This
log severity should be lowered and the message suppressed by default as it is
an expected scenario but causes concern for many users.
{code}
2020-07-17 11:37:38,023 INFO [NiFi Web Server-18]
o.a.n.w.m.IllegalStateExceptionMapper java.lang.IllegalStateException: Access
tokens are only issued over HTTPS. Returning Conflict response.
{code}
A follow-on Jira should address removing the unnecessary request entirely.
> Lower log severity of expected exception for missing content length filter
> size value
> -------------------------------------------------------------------------------------
>
> Key: NIFI-7658
> URL: https://issues.apache.org/jira/browse/NIFI-7658
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.11.4
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Priority: Major
> Labels: error, log, security
>
> Every WAR loaded by NiFi now prints two INFO logs at startup due to the
> default maximum web request size being unpopulated by default. This log
> severity should be lowered and the message suppressed by default as it is an
> expected scenario but causes concern for many users.
> {code}
> 2020-07-17 16:15:46,429 INFO [main] org.apache.nifi.web.server.JettyServer
> Can't parse valid max content length from
> 2020-07-17 16:15:46,429 INFO [main] org.apache.nifi.web.server.JettyServer
> Not adding content-length filter because nifi.web.max.content.size is not set
> in nifi.properties
> {code}
> A follow-on Jira should address removing the unnecessary request entirely.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
