I have a usecase where my service makes HTTP calls to a downstream Java Service .
When these HTTP calls are made using Jetty's Async HTTP Client the Downstream Service sends Connection:close as part of the response headers . This degrades our performance because a new connection is establised for every HTTP request.
When the same HTTP calls are made using Spring Rest Template in a Blocking manner the the Downstream Service sends Connection:keep-alive as part of the response headers .
Any leads on what would could be the reason for server sending Connection:close only in case of Async calls using Jetty HTTP Client ?
