-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing content for multipart request after upgrade to Jetty > 9.2.7 #240
Comments
Closing this issue, as its a duplicate of Issue #182 |
I committed a change for jetty-9.3 and beyond. The change will NOT throw an exception if the content input stream has already been consumed: in this case Request.getParts() will just return an empty collection. However, if the input stream has not already been consumed, the existing multipart parsing behaviour is retained: that is, you may get an exception if the multipart is badly formatted/missing. |
I've just tested it with jetty-9.4.0.v20161208 and it stills fails. Looking at the code the exception is still thrown in line 554: |
@deki please file a new issue. Include how you are using jetty. |
Hmm does it make sense to have three issues for the same root cause? I already described how to reproduce it in #182 |
@deki I've changed my mind. file a new issue. This new issue can be labeled as a regression introduced in the 9.4.0 release. We still need reproduction information though, as the reproduction steps in Issue #182 from Nov 1st still do not apply with the mix of Jetty 9 and Servlet 3.0+ and To state this a different way ... If a servlet is annotated with |
migrated from Bugzilla #480063
status ASSIGNED severity normal in component server for 9.3.x
Reported in version 9.2.7 on platform All
Assigned to: Project Inbox
On 2015-10-18 09:30:22 -0400, Yann Biancheri wrote:
On 2015-10-21 05:24:24 -0400, Jan Bartel wrote:
On 2015-10-28 16:07:39 -0400, Yann Biancheri wrote:
On 2015-10-28 19:54:37 -0400, Jan Bartel wrote:
The text was updated successfully, but these errors were encountered: