Currently if puma server acts as a client with rack-proxy and the response from server through rack-proxy is i.e. 304, then puma skips response body parse step and tcp socket, created by Rack::HttpStreamingResponse, stays opened until process is killed.
Hello @ncr 👋🏻
Currently if
puma
server acts as a client withrack-proxy
and the response from server throughrack-proxy
is i.e.304
, then puma skips response body parse step and tcp socket, created byRack::HttpStreamingResponse
, stays opened until process is killed.More information about this issue is here.
104 fixes this problem