https://bz.apache.org/bugzilla/show_bug.cgi?id=64384
--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> ---
I think I've found the problem, at ContextConfig:1355:
1355 MultipartDef multipartdef = servlet.getMultipartDef();
1356 if (multipartdef != null) {
1357 if (multipartdef.getMaxFileSize() != null &&
1358 multipartdef.getMaxRequestSize()!= null &&
1359 multipartdef.getFileSizeThreshold() != null) {
1360 wrapper.setMultipartConfigElement(new
MultipartConfigElement(
multipartdef.getLocation(),
Long.parseLong(multipartdef.getMaxFileSize()),
Long.parseLong(multipartdef.getMaxRequestSize()),
Integer.parseInt(
multipartdef.getFileSizeThreshold())));
} else {
wrapper.setMultipartConfigElement(new
MultipartConfigElement(
multipartdef.getLocation()));
}
}
When execution reaches 1355, the MultipartDef object contains the expected
values:
maxFileSize=1048576
maxRequestSize=1049600
fileSizeThreshold=null
The predicate on lines 1357 - 1359 cause this configuration to not be applied
if any of the items are missing.
The servlet spec allows any of these items to be missing, so I believe this is
a bug and spec violation together in one.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
