On Tue, Mar 24, 2015 at 11:23 PM, Eric Wong <[email protected]> wrote: > So there might be data sitting on the socket if your application > processing returns a response before it parsed the POST request.
When this occurs, the nginx access logs show an HTTP 200 (OK) response with a 0 byte response body. Is it your hypothesis that the application is just failing to consume the entire POST body in this instance? In that case, wouldn't we expect to see nginx failing to write on the socket instead of read? > Actually, you can try setting up a Rack::Lobster instance but sending > a giant POST request? > > ------------- config.ru -------------- > require 'rack/lobster' > run Rack::Lobster.new > -------------------------------------- I don't know what this is -- systems guy here, not a Rack expert... how will this help? Thanks, --Michael
