If HTTP 1.1 is used and backend doesn't return 'Connection' header, explicitly
return Connection: keep-alive.
add "with custom server logic" to the "Proxying WebSockets" section of the readme.md
http-proxy: 304 responses should emit 'end' too
Merge pull request #337 from indutny/feature-304-end

http-proxy: 304 responses should emit 'end' too
[bench] Remove silly "benchmarks"
[bench] Add a benchmark for websockets throughput
[dist] Update `devDependencies`
[bench] More exact size display
[fix] Handle socket errors
[dist] Bump version to 0.8.6
[fix] Handle errors on request object

Sometimes a request emits `error` event with a `Parse Error`.
[fix] Don't remove `error` listener after response ends

In some rare cases, `error` event might still be emitted after the
response has ended. This is (most likely) a bug in the `node` core.
[dist] Bump version to 0.8.7
fix 'this' reference in routing proxy listener bindings
Fix for retaining large slab buffers in node core
fixed issue #364 'proxyError' event emitted twice
remove offending code, final fix for issue #364
Change wording for handling websocket proxy events
Re-added previous description
Merge pull request #349 from jamie-stackhouse/patch-1

Misleading documentation for Websockets via .createServer