-
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
MultiPart files should be written to disk by default #10936
Comments
A potential fix for it #10937 |
The first version of Jetty that supports EE10 / Servlet 6.0 specs (where this language about fileSizeThreshold value of 0) is Jetty 12 on the ee10 environment. |
Jetty 12 has support for fileSizeThreshold value of 0 in the EE10 environment already. See EE10 handling ... Line 129 in d1da726
Which uses jetty-core handling ... jetty.project/jetty-core/jetty-http/src/main/java/org/eclipse/jetty/http/MultiPartFormData.java Lines 344 to 355 in d1da726
Which is implemented here ... jetty.project/jetty-core/jetty-http/src/main/java/org/eclipse/jetty/http/MultiPartFormData.java Lines 421 to 432 in d1da726
|
Yeah I've just realized that, thx for the quick feedback |
Description
In Jakarta EE 10, the expected behavior when
fileSizeThreshold
is set to0
aka the default value has been clearly specified as you can see in the Javadoc.I quote:
The current behavior of Jetty is not compliant since only strictly positive values are taken into account.
The text was updated successfully, but these errors were encountered: