-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't set maxFormContentSize #4373
Comments
This is by design. You want to set the max form content size on a per-context basis - the lookup as a server attribute is just a rare fallback for those cases where there is no context (some non-typical Jetty embedded usage). |
Duplicate of #4311 |
See #4311 (comment) for details on how to configure |
Reopening. The server configuration facility could still exist.
|
This issue has been automatically marked as stale because it has been a full year without activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to it having no activity. |
9.4.24.v20191120
openjdk11
macOS
User defined value of maxFormContentSize will be ignored.
org.eclipse.jetty.server.handler.ContextHandler set value of maxFormContentSize to default:
_maxFormContentSize = Integer.getInteger(MAX_FORM_CONTENT_SIZE_KEY, DEFAULT_MAX_FORM_CONTENT_SIZE)
In org.eclipse.jetty.server.Request if context is not equal to null, lookup for attributes won't be called.
And the user defined value will be ignored.
The text was updated successfully, but these errors were encountered: