for (the server is allowed to close the
> connection at any point).
> nginx should see this header and not send more data to Jetty (this is
> actually spelled out in the spec)
>
> Joakim Erdfelt / joa...@webtide.com
>
>
> On Tue, Mar 30, 2021 at 11:45 PM Daniel Gredler
> w
Hi,
I'm playing around with a Jetty-based API service deployed to AWS Elastic
Beanstalk in a Docker container. The setup is basically: EC2 load balancer
-> nginx reverse proxy -> Docker container running the Jetty service.
One of the API endpoints accepts large POST requests. As a safeguard, I
e:
>>>
>>>> Daniel,
>>>>
>>>> well that looks wrong! I can confirm your test fails for me!
>>>>
>>>> I find it hard to believe we don't have a test for this... but we have
>>>> changed some close handling recently so o
Hi,
I'm upgrading dependencies in a JAX-RS project, and have reached the point
where I need to upgrade Jersey, which (via transitive dependencies)
involves upgrading Jetty from 9.2.x to 9.4.x.
One of our regression tests verifies that in the case of a request timeout
we are sending an HTTP 408
