Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Problem reading POST body with embedded Jetty 12.0.x

Hi Greg,

Thanks. The particular parts of the application are maintenance oriented and not particularly performance critical but I would love to learn more about this.

For now, my priority lies with getting our application running on Jetty 12. I was expecting to have to do quite some modifications to the application code since we use Jetty in embedded mode. Actually it was a lot easier than I expected and this issue is the last thing that keeps us from moving to Jetty 12. Not bad so far but I would be very happy to get this out of the way.

If you have any suggestions as to what I could do to shed more light on the issue please let me know.



On 12-09-2023 03:01, Greg Wilkins via jetty-users wrote:

Let's get your existing code working.... but then I'd really like to show you how you can use jetty-12 handlers to do that expansion for you prior to any buffering and/or blocking input streams.


On Tue, 12 Sept 2023 at 03:47, Simone Bordet via jetty-users <jetty-users@xxxxxxxxxxx> wrote:

On Mon, Sep 11, 2023 at 2:16 PM Silvio Bierman via jetty-users
<jetty-users@xxxxxxxxxxx> wrote:
> It appears that all handling of POST requests with ZIP-content as
> payload in our application is broken with Jetty 12 (I tried both 12.0.0
> and 12.0.1). We use an embedded Jetty-12 with ee10 and http/2.
> Using Jetty 11 the code works as expected.
> We post a ZIP-file from the command line using Curl to the application.
> The handling code wraps request.getInputStream in a BufferedInputStream
> wrapped in a ZipInputStream and starts reading ZipEntry objects with
> getNextEntry until this returns null. With Jetty 12 this code only
> manages to read the first part of the POST-body and then blocks
> indefinitely. This is not a multi-part request, the ZIP-content is
> simply used as the request payload.
> We have similar handling of ZIP-files posted from inside HTML pages
> (using JS FormData and XmlHttpRequest) and the same thing happens there.
> In this case the FormData is used to create a multi-part POST.
> Each time the first parts of the payload seems to be handled correctly.
> The initial entries are expanded and written to server side files
> correctly.
> No exceptions occur. The code just seems to block indefinitely with no
> CPU activity.
> Any ideas? Perhaps there is something wrong with our embedding code?

Please open an issue with the code example, where it throws, and the
stack trace.
GH issues are better for this kind of analysis.


Simone Bordet
Developer advice, training, services and support
from the Jetty & CometD experts.
jetty-users mailing list
To unsubscribe from this list, visit


jetty-users mailing list
To unsubscribe from this list, visit

Back to the top