Remy what do you mean by...... Specifying everything properly if you expect to parse parts is a lot better.
Did I not do this in the web.xml snippet? <servlet> > <servlet-name>jsp</servlet-name> > > <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> > > <multipart-config> > <location>/web/tmp</location> > <max-file-size>20848820</max-file-size> > <max-request-size>418018841</max-request-size> > <file-size-threshold>1048576</file-size-threshold> > </multipart-config> > > <init-param> > <param-name>fork</param-name> > <param-value>false</param-value> > </init-param> > <init-param> > <param-name>xpoweredBy</param-name> > <param-value>false</param-value> > </init-param> > <load-on-startup>3</load-on-startup> > </servlet> > > <!-- The mappings for the JSP servlet --> > <servlet-mapping> > <servlet-name>jsp</servlet-name> > <url-pattern>*.jsp</url-pattern> > <url-pattern>*.jspx</url-pattern> > <url-pattern>*.vpp</url-pattern> > <url-pattern>*.vsp</url-pattern> > </servlet-mapping> Rick Noel Systems Programmer | Westwood One rn...@westwoodone.com -----Original Message----- From: Rémy Maucherat <r...@apache.org> Sent: Friday, March 28, 2025 10:56 AM To: Tomcat Users List <users@tomcat.apache.org> Subject: [EXT]Re: tomcat 11.0.5 multi-part configuration error On Fri, Mar 28, 2025 at 3:28 PM Rick Noel <rn...@westwoodone.com.invalid> wrote: > > We recently went from an error free tomcat 10 to the latest tomcat > 11.0.5 And now we get a muiti-part configuration error happening. > > The exact error message is this.......... > > org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for > servlet [jsp] threw exception > java.lang.IllegalStateException: Unable to process parts as no > multi-part configuration has been provided > at > org.apache.catalina.connector.Request.parseParts(Request.java:2447) > at > org.apache.catalina.connector.Request.doParseParameters(Request.java:2816) > at > org.apache.catalina.connector.Request.parseParameters(Request.java:2774) > at > org.apache.catalina.connector.Request.getParameter(Request.java:1064) > at > org.apache.catalina.connector.RequestFacade.getParameter(RequestFacade.java:152) > at > org.apache.jsp.record.process.captureandconfirm_vpp._jspService(captur > eandconfirm_vpp.java:221) > > > > Google searches have said to add allowCasualMultipartParsing="true" to the > context.xml file > > Which we now have as....... > <Context allowCasualMultipartParsing="true" > > > And to also define the multi-part configuration in the > tomcat/conf/web.xml > > Which we have now have as..... > <servlet> > <servlet-name>jsp</servlet-name> > > <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> > > <multipart-config> > <location>/web/tmp</location> > <max-file-size>20848820</max-file-size> > <max-request-size>418018841</max-request-size> > <file-size-threshold>1048576</file-size-threshold> > </multipart-config> > > <init-param> > <param-name>fork</param-name> > <param-value>false</param-value> > </init-param> > <init-param> > <param-name>xpoweredBy</param-name> > <param-value>false</param-value> > </init-param> > <load-on-startup>3</load-on-startup> > </servlet> > > <!-- The mappings for the JSP servlet --> > <servlet-mapping> > <servlet-name>jsp</servlet-name> > <url-pattern>*.jsp</url-pattern> > <url-pattern>*.jspx</url-pattern> > <url-pattern>*.vpp</url-pattern> > <url-pattern>*.vsp</url-pattern> > </servlet-mapping> > > > BTW, tomat 10 does successful multi part form submits with out any of above > context.xml or web.xml changes above. > > Is this a bug with tomcat 11.0.5? It is a Servlets specification change, there's no hidden parts parsing anymore. Specifying everything properly if you expect to parse parts is a lot better. Rémy > > > > > > Rick Noel > Systems Programmer | Westwood One > rn...@westwoodone.com > > PLEASE NOTE: This message may contain confidential information and is > intended only for the individual(s) named. Employees of Cumulus Media Inc. > and its subsidiaries (including Westwood One) are prohibited from disclosing > confidential information to any third party. If you are not the named > addressee you should not disseminate, distribute or copy this e-mail. Please > notify the sender immediately by e-mail if you have received this e-mail by > mistake and delete this e-mail from your system. If you are not the intended > recipient you are notified that disclosing, copying, distributing or taking > any action in reliance on the contents of this information is strictly > prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you know the sender and you are sure the content is safe. Please report the message using the Report Message feature in your email client if you believe the email is suspicious.
