[
https://issues.apache.org/jira/browse/ARTEMIS-4939?focusedWorklogId=926724&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-926724
]
ASF GitHub Bot logged work on ARTEMIS-4939:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Jul/24 18:45
Start Date: 19/Jul/24 18:45
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #5103:
URL:
https://github.com/apache/activemq-artemis/pull/5103#issuecomment-2239907314
Don't merge this just yet. I think I'm going to add the ability to configure
the max _response_ header size as well since large request headers may result
in large response headers.
Issue Time Tracking
-------------------
Worklog Id: (was: 926724)
Time Spent: 40m (was: 0.5h)
> Allow configuring request header size for embedded web server
> -------------------------------------------------------------
>
> Key: ARTEMIS-4939
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4939
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In use-cases with large HTTP headers (e.g. using SSO) Jetty can choke on
> large headers and emit a message like:
> {noformat}
> 2024-07-12 11:41:32,875 WARN [org.eclipse.jetty.http.HttpParser] Header is
> too large 8193>8192{noformat}
> This should be configurable in {{bootstrap.xml}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
