-
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
maxFormContentSize Server attributes are not being used with Context #4311
Comments
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd"> That's the DTD for Jetty 7 and Jetty 8. Use: <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "https://www.eclipse.org/jetty/configure_9_3.dtd"> The settings for "Max Form Content Size" belong to the Context (a deployed webapp). If the Request is submitted with The pasted If you just want to configure the Example:
The two attributes on Server [ For context based ones, please use the Context specific options (this is the recommended technique). Example:
If you still need server-wide settings, use the system properties instead.
|
Hi,
I've upgraded maven-jetty-plugin from 9.4.19.v20190610 to the newest release, however sometimes my queries ended with HTTP 400.
I found out, that this version is the latest version that does not ignore
org.eclipse.jetty.server.Request.maxFormContentSize
attribute. Starting from 9.4.20.v20190813, this attribute is ignored.My jetty.xml:
I suspect this PR to broke the behaviour: 2e2cde6
If it's intended change, then documentation should be changed to point out the breaking change.
The text was updated successfully, but these errors were encountered: