Rob Wu dcc64052e3 Change response handling hook ...

When proxyReq is aborted (by us - in response to a redirect response),
it can ultimately trigger an "error" event of type ECONNRESET.
This error was unconditionally propagated to the error handler:
https://github.com/nodejitsu/node-http-proxy/blob/v1.11.1/lib/http-proxy/passes/web-incoming.js#L134-L140

Our proxy error handler responds by writing a response + error code,
which prevents the response from being overwritten.

I found this after upgrading the nock library to 5.2.1+, which contains
510e31c73e
The redirect tests that were previously passing in Node 0.10.x were
failing, with errors like "Can't set headers after they are sent.".

The new implementation makes sure that the proxied response is not
forwarded to the original response.

2017-07-13 17:08:31 +02:00

..

cors-anywhere.js

Change response handling hook

2017-07-13 17:08:31 +02:00

help.txt

Add X-Final-URL

2013-08-29 10:12:03 +02:00

rate-limit.js

Add rate-limiting functionality #45

2016-05-31 00:52:26 +02:00

regexp-top-level-domain.js

Enforce a consistent coding style using eslint

2016-02-26 12:31:35 +01:00