[
https://issues.apache.org/jira/browse/NIFI-12762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865573#comment-17865573
]
Sash Sujith commented on NIFI-12762:
------------------------------------
A bit confused with finding the problem here because in
nifi/nifi-assembly/target/nifi-2.0.0-SNAPSHOT-bin/nifi-2.0.0-SNAPSHOT/conf/nifi.properties,
nifi.web.max.header.size=16 KB
I may just be looking in the wrong place but I couldn't find where the size is
set to 8192 bytes.
> ListenHTTP request headers limited to 8192 bytes
> ------------------------------------------------
>
> Key: NIFI-12762
> URL: https://issues.apache.org/jira/browse/NIFI-12762
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.25.0, 2.0.0-M2
> Reporter: Michael W Moser
> Assignee: Sash Sujith
> Priority: Minor
>
> ListenHTTP will parse HTTP request headers if the property "HTTP Headers to
> receive as Attributes" is set. An HTTP client can sent request headers that
> are larger than the default allowed 8192 bytes, and we get the log message
> {noformat}
> 2024-02-08 20:22:16,548 WARN [ListenHTTP
> (8a290f74-018d-1000-a9d2-c06fdb10e3f3) Web Server-188]
> org.eclipse.jetty.http.HttpParser Header is too large 8193>8192{noformat}
> and ListenHTTP responds with HTTP ERROR 431 Request Header Fields Too Large
> The NiFi UI and REST API sets the max header size to 16384 and it is
> configurable in nifi.properties "nifi.web.max.header.size", in the file
> FrameworkServerConnectorFactory.java.
> We should probably allow ListenHTTP to use the same max header size setting.
> Should we also look into this for HandleHttpRequest?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)