[
https://issues.apache.org/jira/browse/NIFI-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161961#comment-17161961
]
ASF subversion and git services commented on NIFI-7658:
-------------------------------------------------------
Commit 6297310a90f95b90f377729494b29da22b90d320 in nifi's branch
refs/heads/main from Andy LoPresto
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6297310 ]
NIFI-7658 Lowered log severity to DEBUG when web request max content length is
blank.
Signed-off-by: Pierre Villard <[email protected]>
This closes #4415.
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
