proxy-chain - npm Package Compare versions

build/handler_base.js

		@@ -163,3 +163,3 @@ 'use strict';

		// This is to address https://github.com/apifytech/proxy-chain/issues/27
		// This is to address https://github.com/apify/proxy-chain/issues/27
		// It seems that when client closed the connection, the piped target socket
		@@ -166,0 +166,0 @@ // can still pump data to it, which caused unhandled "write after end" error

build/handler_forward.js

		@@ -169,3 +169,3 @@ 'use strict';
		// "RangeError: Invalid status code: 0" (see writeHead in Node's _http_server.js)
		// Fixes https://github.com/apifytech/proxy-chain/issues/35
		// Fixes https://github.com/apify/proxy-chain/issues/35
		if (response.statusCode < 100 \|\| response.statusCode > 999) {
		@@ -179,3 +179,3 @@ this.fail(new _server.RequestError('Target server responded with an invalid HTTP status code (' + response.statusCode + ')', 500));
		// Note that sockets could be closed anytime, causing this.close() to be called too in above statements
		// See https://github.com/apifytech/proxy-chain/issues/64
		// See https://github.com/apify/proxy-chain/issues/64
		if (this.isClosed) return;
		@@ -182,0 +182,0 @@

build/handler_tunnel_chain.js

		@@ -79,3 +79,3 @@ 'use strict';

		// Attempt to fix https://github.com/apifytech/proxy-chain/issues/64,
		// Attempt to fix https://github.com/apify/proxy-chain/issues/64,
		// perhaps the 'connect' event might occur before 'socket'
		@@ -99,3 +99,3 @@ if (!this.trgSocket) {
		// and the detachSocket() call below fails with "Cannot read property '_httpMessage' of null"
		// See https://github.com/apifytech/proxy-chain/issues/63
		// See https://github.com/apify/proxy-chain/issues/63
		if (this.isClosed) return;
		@@ -119,3 +119,3 @@
		// Note that sockets could be closed anytime, causing this.close() to be called too in above statements
		// See https://github.com/apifytech/proxy-chain/issues/64
		// See https://github.com/apify/proxy-chain/issues/64
		if (this.isClosed) return;
		@@ -122,0 +122,0 @@

build/handler_tunnel_direct.js

		@@ -68,3 +68,3 @@ 'use strict';
		// and the detachSocket() call below fails with "Cannot read property '_httpMessage' of null"
		// See https://github.com/apifytech/proxy-chain/issues/63
		// See https://github.com/apify/proxy-chain/issues/63
		if (this.isClosed) return;
		@@ -87,3 +87,3 @@
		// Note that sockets could be closed anytime, causing this.close() to be called too in above statements
		// See https://github.com/apifytech/proxy-chain/issues/64
		// See https://github.com/apify/proxy-chain/issues/64
		if (this.isClosed) return;
		@@ -90,0 +90,0 @@

build/server.js

		@@ -281,3 +281,3 @@ 'use strict';
		// We need to consume socket errors, otherwise they could crash the entire process.
		// See https://github.com/apifytech/proxy-chain/issues/53
		// See https://github.com/apify/proxy-chain/issues/53
		// TODO: HandlerBase will also attach its own 'error' handler, we should only attach this one
		@@ -284,0 +284,0 @@ // if HandlerBase doesn't do it, to avoid duplicate logs

build/tcp_tunnel.js

		@@ -169,3 +169,3 @@ 'use strict';

		// Attempt to fix https://github.com/apifytech/proxy-chain/issues/64,
		// Attempt to fix https://github.com/apify/proxy-chain/issues/64,
		// perhaps the 'connect' event might occur before 'socket'
		@@ -179,3 +179,3 @@ if (!this.trgSocket) {
		// Note that sockets could be closed anytime, causing this.close() to be called too in above statements
		// See https://github.com/apifytech/proxy-chain/issues/64
		// See https://github.com/apify/proxy-chain/issues/64
		if (this.isClosed) return;
		@@ -182,0 +182,0 @@

CHANGELOG.md

		@@ -26,3 +26,3 @@ 0.4.9 / 2021-01-26
		- Added checks for closed handlers, in order to prevent the `Cannot read property 'pipe' of null` errors
		(see issue [#64](https://github.com/apifytech/proxy-chain/issues/64))
		(see issue [#64](https://github.com/apify/proxy-chain/issues/64))

		@@ -32,3 +32,3 @@ 0.4.4 / 2020-03-12
		- Attempt to fix an unhandled exception in `HandlerTunnelChain.onTrgRequestConnect`
		(see issue [#64](https://github.com/apifytech/proxy-chain/issues/64))
		(see issue [#64](https://github.com/apify/proxy-chain/issues/64))
		- Code cleanup
		@@ -39,3 +39,3 @@
		- Fixed unhandled `TypeError: Cannot read property '_httpMessage' of null` exception
		in `HandlerTunnelChain.onTrgRequestConnect` (see issue [#63](https://github.com/apifytech/proxy-chain/issues/63))
		in `HandlerTunnelChain.onTrgRequestConnect` (see issue [#63](https://github.com/apify/proxy-chain/issues/63))

		@@ -58,3 +58,3 @@ 0.4.2 / 2020-02-28
		- BUGFIX: Consume source socket errors to avoid unhandled exceptions.
		Fixes [Issue #53](https://github.com/apifytech/proxy-chain/issues/53).
		Fixes [Issue #53](https://github.com/apify/proxy-chain/issues/53).
		- BUGFIX: Renamed misspelled `Trailers` HTTP header to `Trailer`.
		@@ -61,0 +61,0 @@ - Replaced `bluebird` dependency with native Promises.

package.json

		{
		"name": "proxy-chain",
		"version": "0.4.10-beta.0",
		"version": "0.4.10-beta.1",
		"description": "Node.js implementation of a proxy server (think Squid) with support for SSL, authentication, upstream proxy chaining, and protocol tunneling.",
		@@ -24,6 +24,6 @@ "main": "build/index.js",
		"type": "git",
		"url": "git+https://github.com/apifytech/proxy-chain"
		"url": "git+https://github.com/apify/proxy-chain"
		},
		"bugs": {
		"url": "https://github.com/apifytech/proxy-chain/issues"
		"url": "https://github.com/apify/proxy-chain/issues"
		},
		@@ -30,0 +30,0 @@ "homepage": "https://blog.apify.com/how-to-make-headless-chrome-and-puppeteer-use-a-proxy-server-with-authentication-249a21a79212",

README.md

		@@ -269,2 +269,8 @@ # Programmable HTTP proxy server for Node.js

		The optional `options` parameter is an object with the following properties:
		- `port: Number` - Enables specifying the local port to listen at. By default `0`,
		which means a random port will be selected.
		- `hostname: String` - Local hostname to listen at. By default `localhost`.
		- `verbose: Boolean` - If `true`, the functions logs a lot. By default `false`.

		The result of the function is a local endpoint in a form of `hostname:port`.
		@@ -271,0 +277,0 @@ All TCP connections made to the local endpoint will be tunneled through the proxy to the target host and port.

New alerts