tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 54917] More relaxation on HttpServletRequest.getParts()
Date Wed, 01 May 2013 23:11:00 GMT

Konstantin Kolinko <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #2 from Konstantin Kolinko <> ---
The use of "multipart/form-data" is defined by HTML specification (HTML 4.0
onwards). It was first specified by RFC2388.


Regarding the description of @MultipartConfig (chapter 8.1.5 of Servlet 3.0
Rev.a), I think that 
a) maybe we could report it and ask it to be corrected as an editorial error
b) this wording is just in line with how the configuration option was named
simply "multipart config" and not "multipart form data config". (As to be open
for further wider use in the future or in different contexts).

It is just a configuration option. How this option is interpreted and used is
defined elsewhere: in chapter 3.2, as you correctly noted.

Thus I see no provision why Tomcat should ever try to process any other
multipart mime-type. (Unless one is about to follow "Zawinski's Law", ).

I am closing this as WONTFIX.

> disagreeing implementations in Tomcat vs. GlassFish

What is so different in Glassfish?

> my current processing hack using JavaMail

Using an e-mail library to process an e-mail format is quite reasonable. Note
though that a) JavaMail is just a standard, an API. There exist different
independent implementations of it. b) There exist different libraries that can
parse mime formats.

If you start a thread on the users mailing list or elsewhere, maybe people can
come up with better options.

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message