[NIFI-7658] Lower log severity of expected exception for missing content length filter size value

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.11.4
• Fix Version/s: 1.12.0
• Component/s: Core Framework
• Labels: error log security
• Assignee: Andy LoPresto
• Reporter: Andy LoPresto
• Created: 17/Jul/20 21:04
• Updated: 21/Jul/20 11:43
• Resolved: 21/Jul/20 11:43

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.

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

A follow-on Jira should address removing the unnecessary request entirely.

Issue Links

• is a clone of: NIFI-7657 Lower log severity of expected exception for authentication on unsecured instance
• links to: GitHub Pull Request #4415