…ool would not catch the error and crash. That's not a nice thing to do, so now just destroy the request.
Fixed problem: When a keep-alive connection has many requests, each request can result in a separate bounce, and all of those bounces getting piped back into the request stream can result in ugly warnings on stdout: (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. Trace: at Socket.<anonymous> (events.js:126:17) at Socket.pipe (stream.js:156:8) at /Users/seth/development/service/node_modules/bouncy/index.js:86:20 at /Users/seth/development/service/scalar.js:52:5 at IncomingMessage.onHeaders (/Users/seth/development/service/node_modules/bouncy/index.js:46:13) at IncomingMessage.emit (events.js:64:17) at Parser.<anonymous> (/Users/seth/development/service/node_modules/bouncy/node_modules/parsley/lib/modes.js:135:21) at Parser.execute (/Users/seth/development/service/node_modules/bouncy/node_modules/parsley/index.js:20:35) at Socket.<anonymous> (/Users/seth/development/service/node_modules/bouncy/node_modules/parsley/index.js:11:14) at Socket.emit (events.js:64:17)