…o the paths being requested.
fix loop typo another typo *sigh* this wasn't doing what I thought it was doing.
…rts (e.g. 80, 443). solution: support privilege drop after socket bind via new --user <username> parameter.
…DELETE requests. Fixes #338.
…TE requests with no "Content-Length" header. Fixes #373.
…or external sites. Fixes #359.
If HTTP 1.1 is used and backend doesn't return 'Connection' header, expicitly return Connection: keep-alive.
… node 0.8.x. On node 0.6.x the support was opaque via port, but on the new node, socketPath should be set explicitely. - avoid adding multiple headers with the same name - fix bug in setting connection
add "with custom server logic" to the "Proxying WebSockets" section of the readme
…rs more than once when proxying websocket requests." This reverts commit a681493.
…than once when proxying websocket requests.