https://bz.apache.org/bugzilla/show_bug.cgi?id=63206
--- Comment #7 from Andy Wilkinson <awilkin...@pivotal.io> --- > Because it can be set by the application and is not configured and/or managed > by Tomcat. That was a distinction that you did not make when you stated the following: > Tomcat shouldn't be creating directories unless explicitly directed to do so. Even with that new distinction, I'm not sure that I agree. Why should a usability benefit that is applied to Tomcat itself not also applied to an application that is deployed to Tomcat? Put another way, what harm could be caused by creating the directory? It's also possible that the application does not customise the location via <multipart-config> or @MultipartConfig. In that case the location is both configured and managed by Tomcat yet the directory will not be created. That seems unnecessarily inconsistent to me. -- 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
