Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-7658

Lower log severity of expected exception for missing content length filter size value

    XMLWordPrintableJSON

    Details

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                alopresto Andy LoPresto
                Reporter:
                alopresto Andy LoPresto
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m