That's reassuring in a way :-)
It sounds to me you are trying with HTTP/1.1 something you would normally do with HTTP/2.
When the server sends a response (and a status code), NGINX may rightfully stop sending more stuff to the server. Can you tell Jetty to send its reply (including the status code) only AFTER all data has been received?
If a final status code is delivered (probably with a Connection: close header), it is fine to close the request channel as well.
My guess is you should look at HTTP/2 or Websockets.
--j.
It sounds to me you are trying with HTTP/1.1 something you would normally do with HTTP/2.
When the server sends a response (and a status code), NGINX may rightfully stop sending more stuff to the server. Can you tell Jetty to send its reply (including the status code) only AFTER all data has been received?
If a final status code is delivered (probably with a Connection: close header), it is fine to close the request channel as well.
My guess is you should look at HTTP/2 or Websockets.
--j.