Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] "no content" timeout exception while upl multipart file on 9.3.12 - 9.3.13 - 9.3.14?


On Tue, Nov 8, 2016 at 12:32 PM, Michele Rossi <michele.rossi@xxxxxxxxx> wrote:
> hi,
> I have enabled the Jetty low-level logs and now HTTP2 negotiations and
> traffic are visible but I am far from understanding what's going on :)
> I have attached the logs here in case a good soul out there feels like
> taking a look (if it benefits the project too).
> For now we have resolved our problem by disabling HTTP2 on the client making
> this particular multipart upload request.

What client are you using ?

I ask because the logs show that the last DATA frame (line 12305)
arrives with the last 48 bytes that would make the total of 1489449
bytes as specified by the Content-Length, but that DATA frame has
end=false, while it should have end=true.

Because there is no indication that the stream has ended, Jetty waits
for more data from the client until it times out.

In HTTP/2 the framing is done by the end stream flags, not by the fact
that the Content-Length has been reached.

It appears to me a client bug.

Simone Bordet
Developer advice, training, services and support
from the Jetty & CometD experts.

Back to the top