proxy-chain - npm Package Compare versions

Comparing version 2.0.4 to 2.0.5-beta.0

dist/server.js

@@ -262,3 +262,8 @@ "use strict";
             // CONNECT server.example.com:80 HTTP/1.1
-            handlerOpts.trgParsed = new url_1.URL(`connect://${request.url}`);
+            try {
+                handlerOpts.trgParsed = new url_1.URL(`connect://${request.url}`);
+            }
+            catch {
+                throw new request_error_1.RequestError(`Target "${request.url}" could not be parsed`, 400);
+            }
             if (!handlerOpts.trgParsed.hostname || !handlerOpts.trgParsed.port) {
@@ -265,0 +270,0 @@ throw new request_error_1.RequestError(`Target "${request.url}" could not be parsed`, 400);

package.json

 {
   "name": "proxy-chain",
-  "version": "2.0.4",
+  "version": "2.0.5-beta.0",
   "description": "Node.js implementation of a proxy server (think Squid) with support for SSL, authentication, upstream proxy chaining, and protocol tunneling.",
@@ -5,0 +5,0 @@ "main": "dist/index.js",

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

164849

increased by0.18%

Lines of code

1685

increased by0.3%

Worsened metrics

Number of low quality alerts

1

increased byInfinity%

No dependency changes