Thanks for replies yes we do have mismatch using jaxrs-Jersey Api and Tomcat Filter causes issues so when choose to use Jersey filters it works fine and makes sense after seeing the responses.
On Tue, 17 Dec, 2024, 12:51 am Christopher Schultz, < ch...@christopherschultz.net> wrote: > Mark, > > On 12/16/24 5:52 AM, Mark Thomas wrote: > > On 16/12/2024 10:10, anand raj wrote: > >> Hi all, > >> > >> In Tomcat 11 a jersey Api multipart-formdata is registered with > Multipart > >> feature.Also an inbound filter in front reading request.getparamater > >> fails > >> with "unable to process parts as no multi-part configuration has been > >> provided." > >> In Tomcat 11 it fails. > >> In Tomcat 10 same setup works continuing parts as empty list. > >> > >> Is this expected > > > > Yes. > > > >> and valid change > > > > Yes. > > > > Parameter parsing in the Servlet spec has been tightened up to fail with > > an exception rather than to ignore errors and carry on. > > More specifically, these requests were /actually failing/ in Tomcat 10 > and not producing any warnings or errors. So the difference is that you > know about the failures, now. > > >> and if so any suggestion how to avoid this? > > > > If you want Tomcat to parse the form data then either: > > > > - configure the target servlet to support multi-part > > > > or > > > > - set allowCasualMultipartParsing="true" on the Context > > > > > > If you don't want Tomcat to parse the form data: > > > > - don't call any of the getParameter*() methods > > - read the body using getInputStream() > > - parse the body manually. > > -chris > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
