Skip to content

Latest commit

 

History

History
247 lines (203 loc) · 10 KB

CHANGELOG.md

File metadata and controls

247 lines (203 loc) · 10 KB

2.0.1 / 2022-05-02

  • Simplify code, fix tests, move to TypeScript #162
  • Bugfix: Memory leak in createTunnel #160
  • Bugfix: Proxy fails to handle non-standard HTTP response in HTTP forwarding mode, on certain websites #107
  • Pass proxyChainId to tunnelConnectResponded #173
  • feat: accept custom port for proxy anonymization #214
  • fix: socket close race condition
  • feat: closeConnection by id #176
  • feat: custom dns lookup #175

1.0.3 / 2021-08-17

  • Fixed EventEmitter memory leak (see issue #81)
  • Added automated tests for Node 16
  • Updated dev dependencies

1.0.2 / 2021-04-14

  • Bugfix: closeTunnel() function didn't work because of runningServers[port].connections.forEach is not a function error (see issue #127)

1.0.1 / 2021-04-09

  • Bugfix: parseUrl() result now always includes port for http(s), ftp and ws(s) (even if explicitly specified port is the default one) This fixes #123.

1.0.0 / 2021-03-17

  • BREAKING: The parseUrl() function slightly changed its behavior (see README for details):
    • it no longer returns an object on invalid URLs and throws an exception instead
    • it URI-decodes username and password if possible (if not, the function keeps the username and password as is)
    • it adds back auth property for better backwards compatibility
  • The above change should make it possible to pass upstream proxy URLs containing special characters, such as http://user:pass:[email protected] or http://us%35er:[email protected]. The parsing is done on a best-effort basis. The safest way is to always URI-encode username and password before constructing the URL, according to RFC 3986. This change should finally fix issues: #89, #67, and #108
  • BREAKING: Improved error handling in createTunnel() and prepareRequestFunction() functions and provided better error messages. Both functions now fail if the upstream proxy URL contains colon (:) character in the username, in order to comply with RFC 7617. The functions now fail fast with a reasonable error, rather later and with cryptic errors.
  • BREAKING: The createTunnel() function now lets the system assign potentially random listening TCP port, instead of the previous selection from range from 20000 to 60000.
  • BREAKING: The undocumented findFreePort() function was moved from tools.js to test/tools.js
  • Added the ability to access proxy CONNECT headers for proxy tunneling.
  • Removed dependency on Node.js internal modules, hopefully allowing usage of this library in Electron.
  • Got rid of the "portastic" NPM package and thus reduced bundle size by ~50%
  • Various code improvements and better tests.
  • Updated packages.

0.4.9 / 2021-01-26

  • Bugfix: Added back the scheme field to result from parseUrl()

0.4.8 / 2021-01-26

  • Bugfix: parseUrl() function now handles IPv6 and other previously unsupported URLs. Fixes issues #89 and #67.

0.4.7 / 2021-01-19

  • Bugfix: closeTunnel() function was returning invalid value. see PR #98.

0.4.6 / 2020-11-09

  • Proxy.Server now supports port: 0 option to assign the port randomly, see PR #98.
  • anonymizeProxy() now uses the above port assignment rather than polling for random port => better performance
  • Updated NPM packages

0.4.5 / 2020-05-15

  • Added checks for closed handlers, in order to prevent the Cannot read property 'pipe' of null errors (see issue #64)

0.4.4 / 2020-03-12

  • Attempt to fix an unhandled exception in HandlerTunnelChain.onTrgRequestConnect (see issue #64)
  • Code cleanup

0.4.3 / 2020-03-08

  • Fixed unhandled TypeError: Cannot read property '_httpMessage' of null exception in HandlerTunnelChain.onTrgRequestConnect (see issue #63)

0.4.2 / 2020-02-28

  • Bugfix: Prevented attempted double-sending of certain HTTP responses to client, which might have caused some esoteric errors
  • Error responses now by default have Content-Type: text/plain; charset=utf-8 instead of text/html; charset=utf-8 or missing one.

0.4.1 / 2020-02-22

  • Increased socket end/destroy timeouts from 100ms to 1000ms, to ensure the client receives the data.

0.4.0 / 2020-02-22

  • BREAKING CHANGE: Dropped support for Node.js 9 and lower.
  • BUGFIX: Consume source socket errors to avoid unhandled exceptions. Fixes Issue #53.
  • BUGFIX: Renamed misspelled Trailers HTTP header to Trailer.
  • Replaced bluebird dependency with native Promises.
  • Upgraded NPM dev dependencies.
  • Fixed broken tests caused by newly introduced strict HTTP parsing in Node.js.
  • Fixed broken test on Node.js 10 by adding NODE_OPTIONS=--insecure-http-parser env var to npm test.

0.3.3 / 2019-12-27

  • More informative messages for "Invalid upstreamProxyUrl" errors

0.3.2 / 2019-09-17

  • Bugfix: Prevent the "TypeError: hostHeader.startsWith is not a function error in HandlerForward by not forwarding duplicate Host headers

0.3.1 / 2019-09-07

  • BREAKING CHANGE: closeAnonymizedProxy throws on invalid proxy URL
  • Bugfix: Attempt to prevent the unhandled "write after end" error
  • Bugfix: Proxy no longer attempts to forward invalid HTTP status codes and fails with 500 Internal Server Error
  • Fixed closing of sockets on Node 10+
  • Fixed and improved unit tests to also work on Node 10+, update dev dependencies
  • Changed HTTP 200 message from Connection established to Connection Established to be according to standards
  • Proxy source/target sockets are set to no delay (i.e. disabled Nagle's algorithm), to avoid any caching delays
  • Improved logging

0.2.7 / 2018-02-19

  • Updated README

0.2.6 / 2018-12-27

  • Bugfix: Added Host header to HTTP CONNECT requests to upstream proxies

0.2.5 / 2018-09-10

  • Bugfix: Invalid request headers broke proxy chain connection. Now they will be skipped instead.

0.2.4 / 2018-07-27

  • Bugfix: large custom responses were not delivered completely because the socket was closed too early

0.2.3 / 2018-06-21

  • Bugfix: 'requestFailed' was emitting { request, err } instead of { request, error }

0.2.2 / 2018-06-19

  • BREAKING: The 'requestFailed' event now emits object { request, error } instead of just error

0.1.35 / 2018-06-12

  • Bugfix: When target URL cannot be parsed instead of crashing, throw RequestError

0.1.34 / 2018-06-08

  • Minor improvement: HandlerBase.fail() now supports RequestError

0.1.33 / 2018-06-08

  • Renamed customResponseFunc to customResponseFunction and changed parameters for more clarity

0.1.32 / 2018-06-08

  • Added customResponseFunc option to prepareRequestFunction to support custom response to HTTP requests

0.1.31 / 2018-05-21

  • Updated project homepage in package.json

0.1.29 / 2018-04-15

  • Fix: anonymizeProxy() now supports upstream proxies with empty password

0.1.28 / 2018-03-27

  • Added createTunnel() function to create tunnels through HTTP proxies for arbitrary TCP network connections (eq. connection to mongodb/sql database through HTTP proxy)

0.1.27 / 2018-03-05

  • Better error messages for common network errors
  • Pass headers from target socket in HTTPS tunnel chains

0.1.26 / 2018-02-14

  • If connection is denied because of authentication error, optionally "prepareRequestFunction" can provide error message.

0.1.25 / 2018-02-12

  • When connection is only through socket, close srcSocket when trgSocket ends

0.1.24 / 2018-02-09

  • Fixed incorrect closing of ServerResponse object which caused phantomjs to mark resource requests as errors.

0.1.23 / 2018-02-07

  • Fixed missing variable in "Incorrect protocol" error message.

0.1.22 / 2018-02-05

  • Renamed project's GitHub organization

0.1.21 / 2018-01-26

  • Added Server.getConnectionIds() function

0.1.20 / 2018-01-26

  • Fixed "TypeError: The header content contains invalid characters" bug

0.1.19 / 2018-01-25

  • fixed uncaught error events, code improved

0.1.18 / 2018-01-25

  • fixed a memory leak, improved logging and consolidated code

0.1.17 / 2018-01-23

  • added connectionClosed event to notify users about closed proxy connections

0.1.16 / 2018-01-09

  • added measuring of proxy stats - see getConnectionStats() function

0.1.14 / 2017-12-19

  • added support for multiple headers with the same name (thx shershennm)

0.0.1 / 2017-11-06

  • Project created